Bug
Editing branch versioned data with cascading attribute rules returns the error "ORA-00001: unique constraint <value> violated" if the feature being edited has a large number of vertices.
| Bug ID Number | BUG-000172060 |
|---|---|
| Submitted | November 6, 2024 |
| Last Modified | September 8, 2025 |
| Applies to | ArcGIS GIS Server |
| Version found | 11.3 |
| Operating System | N/A |
| Operating System Version | N/A |
| Version Fixed | 3.5, 3.2.5, 3.3.6, 3.4.4 |
| Status | Fixed |
Additional Information
This issue is fixed in ArcGIS Pro 3.5, 3.2.5, 3.3.6, and 3.4.4.Workaround
The Oracle constraint error happens when same-moment updates are triggered in branch versioning; this triggers in any situation, attribute rules, split, merge, or custom tools. In some cases, if an attribute rule is involved, the rule can be rewritten to avoid the extra update, but it is a bug in the software. This has been fixed in 11.5 (Oracle-specific bug) and will be patched in ArcGIS Enterprise 10.9.1, 11.1, and 11.3 as data management patches.
Steps to Reproduce
Bug ID: BUG-000172060
Software:
- ArcGIS GIS Server
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App