Bug
When enabling archiving on a featureclass that has a user defined index in Oracle, then disabling (while keeping the previous archive table), the next time archiving is enabled, the User defined index is not created successfully.
| Bug ID Number | NIM013312 |
|---|---|
| Submitted | November 29, 2007 |
| Last Modified | April 2, 2025 |
| Applies to | No Product Found |
| Version found | 9.2 |
| Version Fixed | 9.4 |
| Status | Fixed |
Description
When enabling archiving on an object class or feature classes in Oracle, user defined attribute indexes are not created on the new archive class.Cause
When enabling archiving on an object class or feature class, user defined indexes are not created on the archive class, because of internal ArcSDE errors when creating the archive class.Workaround
To workaround the issue, manually create the user defined index on the archive class in the underlying DBMS using the CREATE INDEX statement.For example, if the object class contained an index on the owner attribute, then the same index needs to be created manually on the archive class table's owner attribute.
Without the index on the archive class, queries using the non-indexed archive class table attribute may encounter poor performance.
Steps to Reproduce
Bug ID: NIM013312
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