laptop and a wrench

Bug

A numeric primary key is automatically adopted as the ObjectID when registering a spatial table in Oracle with a geodatabase.

Last Published: May 30, 2017 ArcSDE/Enterprise Geodatabase
Bug ID Number BUG-000099797
SubmittedOctober 4, 2016
Last ModifiedJune 5, 2024
Applies toArcSDE/Enterprise Geodatabase
Version found10.2.2
StatusDuplicate

Additional Information

Duplicate of BUG-000088358: Addressed in 10.5 by BUG-000088358

Workaround

Workaround 1: Create the table with a unique constraint rather than a primary key constraint and register it with the geodatabase. This results in a dialog box prompting the user if they would like to use the unique numeric field or create a new OID field.Workaround 2: Use the ArcSDE command line tools 'sdelayer -o register' with the '-C' option to specify if the row ID is to be registered as user maintained or ArcSDE maintained.

Steps to Reproduce

Bug ID: BUG-000099797

Software:

  • ArcSDE/Enterprise Geodatabase

Get notified when the status of a bug changes

Download the Esri Support App

Discover more on this topic

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options