Is This Content Helpful?
We're glad to know this article was helpful.
Synchronizing new records into an Oracle geodatabase where some of the records exist may create incorrect or duplicate GlobalID values.
This issue only affects Oracle geodatabases and can occur in cases when performing geodatabase synchronization. If the geodatabase synchronization from the parent or child replica includes features or rows which already exist in the target geodatabase being synchronized, the problem can be encountered.
One scenario when this case can occur is when applying multiple generations of delta files in one direction without sending acknowledgements back to the origin replica geodatabase.
If there is suspicion that this has occurred, Esri recommends checking the GlobalID values for duplicates.
Esri has identified the following issue: BUG-000091883: Syncing in cases where some inserts are applied as updates causes incorrect / duplicate GlobalIDs to be set.
Inspect the data for duplicate GlobalID values.
A script for checking for the presence of duplicate GlobalIDs is available here: HowTo: Check an Oracle geodatabase for duplicate GlobalID values
This issue has been fixed in ArcGIS 10.4 and the following patches:
• ArcGIS 10.3.1 for (Desktop, Engine, Server) Feature Service Sync Performance Patch
• ArcGIS 10.2.1 for (Desktop, Engine, Server) Utilities and Telecom Update 5 Patch
Please contact Esri Support Services if duplicate GlobalID values are encountered.