Importing an XML Workspace document or copying data from a relationship class within an ArcSDE Oracle database into a File-GDB or Personal GDB produces two field indexes on one table with the same name.
Last Published: August 25, 2014ArcSDE/Enterprise Geodatabase
Bug ID Number
NIM056409
Submitted
April 16, 2010
Last Modified
April 2, 2025
Applies to
ArcSDE/Enterprise Geodatabase
Version found
9.3.1
Status
Duplicate
The issue is a duplicate of an existing issue. See the issue's Additional Information section for details. Customers associated with the duplicate issue are automatically attached to the open issue.
Additional Information
NIM051114
Workaround
There are a few workarounds for this behavior:1. Use application server connection when exporting to the file geodatabase.2. Insure that index names in the source Oracle geodatabase are very unique to start with, not just at the end of their names.3. Drop and recreate the indexes with unique names after the export to file geodatabase.