Is This Content Helpful?
We're glad to know this article was helpful.
Why does my check-in fail when I set the flag CreateOIDMappingTable to TRUE?
Programmatically setting the CreateOIDMappingTable flag to TRUE enables you to create two DBMS tables on check-in that record the ObjectIDs of features that have been modified or added to the checkout geodatabase.
The names of these tables will be automatically generated from the name of the checkout with the suffix "_OM" or "_RC", for example, "MyCheckOut_OM". This _OM table will record the ObjectIDs of new features added to the checkout geodatabase and also how these new feature ObjectIDs are mapped to ObjectIDs for the same new features created in the master geodatabase.
All the changes made in the checkout geodatabase, such as inserts, updates, and deletes, are additionally recorded in a separate table, the name of which will also be automatically generated with the name of the checkout with the suffix "_RC".
If the name of the checkout and the suffix "_OM" or "_RC" exceeds your DBMS limitation for a tablename, this can cause the check-in operation to fail.