AnsweredAssumed Answered

Use existing objectid fails

Question asked by kmjones on Aug 30, 2017
Latest reply on Aug 31, 2017 by kmjones

Hi there,
I have a large database I'm designing in Oracle 11g. I am missing something when I create the new tables with the OBJECTID. I create empty tables via SQL in oracle, then open ArcMap 10.3 to manage ->register with geodatabase.
No matter what I do, it will not recognize OBJECTID as the objectid field.
It consistently uses the second column REGION_CODE. I have even changed REGION_CODE to a VARCHAR and it still ignores OBJECTID and creates a ESRI_OID filed instead.

I have created OBJECTID as NUMBER(38) UNIQUE, NOT NULL per all the documentation.
REGION_CODE is the primary key. Any hints on getting ESRI to recognize the OBJECTID as the object id type is most appreciated. I know OBJECTID should never be the primary key. Thank you in advance  ~ Kathy

 

CREATE TABLE REGION
(
OBJECTID NUMBER(38) NOT NULL
, REGION_CODE NUMBER(38) NOT NULL
, REGION_NAME VARCHAR2(30 CHAR) NOT NULL
, EFFECTIVE_DATE_START DATE
, EFFECTIVE_DATE_END DATE
, COMMENTS VARCHAR2(255 CHAR)
, LAST_UPDATE_DATE DATE
, LAST_UPDATE_BY VARCHAR2(50 CHAR)
, SHAPE MDSYS.SDO_GEOMETRY
, CONSTRAINT REGION_PK PRIMARY KEY
(
REGION_CODE
)
ENABLE
);

ALTER TABLE REGION
ADD CONSTRAINT REGION_OID UNIQUE
(
OBJECTID
)
ENABLE;

Outcomes