Bug
Inconsistent behavior is observed in ArcGIS while working with non-spatial ArcSDE views or Oracle views.
| Bug ID Number | NIM005470 |
|---|---|
| Submitted | December 9, 2006 |
| Last Modified | April 2, 2025 |
| Applies to | No Product Found |
| Version found | 9.2 |
| Version Fixed | 9.3 |
| Status | Fixed |
Workaround
1) Have an objectid number(38) not null field in the veiw. Then register the view with Geodatabase using the existing objectid field. Once registered, everything works.If a view does not have an objectid number(38) not null field, then registering with geodatabase fails with many reasons like proper privileges.For sql server users, the above workaround does not work as sql server has some reservations in creating indexes for views.Since with 9.1, all geoprocessing tools were working with non-spatial views, some users are having big trouble as their workflow demands use of views in model bldr.Another user reported the same problem today. Fortunately he works with tables (not views), having those tables registered with geodatabase made his models run correctly again. However he has to change his scripts that was updating the tables everyday.Miner & Miner has mxd with joins to oracle views not registered with ArcSDE. At 9.1 they were able to edit their FCs that have these joins defined; at 9.2 they are getting a network I/O error. For now they are using the OLEDB suggested workaround but they have stated that this can only be a temporary solution. (Cheryl C 01/23/07)Steps to Reproduce
Bug ID: NIM005470
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