Bug
Updating a NULL geometry on a non-versioned feature class stored in Oracle does not correctly update the business table Spatial Column attribute.
| Bug ID Number | NIM012274 |
|---|---|
| Submitted | October 11, 2007 |
| Last Modified | June 5, 2024 |
| Applies to | No Product Found |
| Version found | 9.2 |
| Version Fixed | 9.3 |
| Status | Fixed |
Description
Updating a NULL geometry using ArcMap fails when the data is stored using SDEBINARY and the feature class is non-versioned.Cause
This is a known issue.When updating a NULL geometry for a non-versioned feature class stored using SDEBINARY, the value for the spatial column in the business table is set to 0 while the feature and spatial table's fid values are set correctly. The result is a record in the business table with no corresponding geometry.
Additionally, if the editor attempts to update another geometry the value for the spatial column is again set to 0 violating the unique constraint.
Workaround
Register the feature class as versioned.Steps to Reproduce
Bug ID: NIM012274
Software:
- No Product Found
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