topic Re: underlying dbms error ora-00001 unique constraint violated in Data Management Questions

underlying dbms error ora-00001 unique constraint violated

hananelyan — Wed, 31 Jul 2013 06:10:50 GMT

Dear All

Please help me with my new problem in ArcSDE geodatabase ,
I have layer name it landuse when i unregisterd layer the message appear
underlying dbms error ora-00001 unique constraint (GAM.A6_D910) violated GAM.LANDUSE

I did the post and reconcile to all my data base and then compress it , the post and reconcile succsefully and the compress succesfully but when i check unregisterd as vesion for landuse layer the messgae appear
underlying dbms error ora-00001 unique constraint (GAM.A6_D910) violated GAM.LANDUSE

thank you

Re: underlying dbms error ora-00001 unique constraint violated

AsrujitSengupta — Wed, 31 Jul 2013 15:44:58 GMT

Hanan,

I would suggest creating a full backup of your geodatabase and then running the "sdegdbrepair -o diagnose_tables" to look for any orphaned records.

If any orphaned records are found, you can run "sdegdbrepair -o repair_tables" to correct those records.

Hope this helps!

Regards,

Re: underlying dbms error ora-00001 unique constraint violated

hananelyan — Sat, 03 Aug 2013 06:13:58 GMT

Dear All
The previous problem was solved.
But now when I work post and reconcile , and then I work compress , compress has been successfully but virtually no compress because when I inquired at the Oracle gives no records, no compress that has been done successfully, knowing that I killed all users .
thenk you

Re: underlying dbms error ora-00001 unique constraint violated

RedaAli — Wed, 09 Apr 2014 06:34:45 GMT

Hi Hanan ,

Would you mind inform us,
How did you solve the first problem?

Thanks
Reda Ali

Re: underlying dbms error ora-00001 unique constraint violated

AsrujitSengupta — Wed, 09 Apr 2014 13:31:44 GMT

I would suggest creating a full backup of your geodatabase and then running the "sdegdbrepair -o diagnose_tables" to look for any orphaned records.

If any orphaned records are found, you can run "sdegdbrepair -o repair_tables" to correct those records.

As suggested in the second post of this thread, run the sdegdbrepair utilities and let us know if that helps!