Is This Content Helpful?
We're glad to know this article was helpful.
This issue has been resolved in ArcGIS 10 (Desktop, Engine, Server) Service Pack 1 and in an ArcSDE 9.3.1 Service Pack 2 General Update Patch. Please see the links in the Related Information section below.
"ORA-00001: unique constraint (LOCAL.A18_PK) violated"
This bug does NOT occur in the following situations:
• Using a release prior to 9.3.1 SP2 (9.3.1 SP1 and earlier).
• Using geodatabase replication with ArcSDE for SQL Server or ArcSDE for Postgres.
• Using simple one-way replication to non-versioned data or check-out/check-in replication where the data on the parent is not versioned.
• Using check-out/check-in replication where the data does not have globalids.
This issue is also encountered when using the data change's components from the geodatabase distributed object model to import inserts when the data includes globalids.
Corruption that has occurred in one geodatabase can be applied to a relative replica geodatabase through synchronize. In these cases, it is important to consider the relative replica geodatabases as well.
The synchronization incorrectly attempts to insert invalid objectids. The objectid values that are applied for inserts are unpredictable and are not obtained from the classes rowid generator.
A link to ArcGIS 10 Service Pack 1 is provided in the Related Information section.
A link to ArcSDE 9.3.1 Service Pack 2 General Update Patch is provided in the Related Information section.