laptop and a wrench

Bug

Exporting Schematic datasets from personal geodatabases to file geodatabases (and vice versa) results in diagrams with broken links and missing features.

Last Published: August 25, 2014 ArcSDE Personal
Bug ID Number NIM090765
SubmittedApril 19, 2013
Last ModifiedJune 5, 2024
Applies toArcSDE Personal
Version foundNo Version Found
StatusKnown Limit

Additional Information

2 work-arounds exist depending on the version involved.

Workaround

Upgrade to 10.1 SP1 and install the Schematic Migration Patch:<a href="http://support.esri.com/en/downloads/patches-servicepacks/view/productid/160/metaid/1971" target="_blank">http://support.esri.com/en/downloads/patches-servicepacks/view/productid/160/metaid/1971</a>If you can't upgrade to 10.1 SP1 and the migration patch, then you need to export in multiple steps. 1. Export just the definitions.2. In the new database, show/hide the schematic classes.3. For each schematic edge class, use the indexes tab on the properties page and delete the spatial index.4. Export the diagrams to this new database.*Note that unless the classIDs exactly match for the source and destination databases, then GUIDs must be used. GUIDs must be enabled on the geometric network and all diagrams must have the GUIDs appropriately updated. Then during export, use the GUID option instead of the FCID and FOID option. It is a bit slower for the export, but far more accurate.

Steps to Reproduce

Bug ID: NIM090765

Software:

  • ArcSDE Personal

Get notified when the status of a bug changes

Download the Esri Support App

Discover more on this topic

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options