Upgrade Metadata Crashes ArcCatalog

[GavinMcDade]

While using the Upgrade Metadata tool in a recently upgraded ArcSDE 10/Oracle 11g database, I've encountered two feature classes that produce an ArcCatalog Application error.  I can see in the geoprocessing tool output window that it runs into trouble just as it begins the actual ESRITranslator (FGDC to ArcGIS) task.  Dismissing the error window results in ArcCatalog simply shutting down, entirely, with no further error messages provided.  I even exported the feature classes to a File GDB and tried running the Upgrade Metadata tool in that setting �?? but, with the same results.  Any ideas as to what ArcCatalog might find so offensive about metadata content that it would pack up its toys and go home? 

Thx.

Gavin

[GavinMcDade]

Update:

While trying a random thing or two, I seem to have "fixed" the problem, although it makes little sense to me.  Here's what I found: 

1. If I imported (in hopes of overwriting) the metadata for the feature class from a duplicate copy in our production SDE database (I'm working in our development SDE), purposely using the wrong translator/import type (FROM_ISO_19139 instead of FGDC), I could get the FC to "think" it was an ISO format - although, it no longer displayed the Summary and Description info.

2. I then ran the Upgrade Metadata tool again, this time using the [ESRIISO_TO_ARCGIS] Upgrade Type.  The upgrade completed successfully, albeit w/o the aforementioned information.

3. I DELETED the upgraded feature class from my Dev database, then replaced it by copy/pasting from my (non-upgraded) Prod source.

4. Oddly, even though the feature class was completely removed from the database, the pasted replacement (with its full metadata intact, of course) is still regarded by ArcCatalog as having been upgraded.

I'm happy.  ArcCatalog is happy (I think).  And no hand reached out from the metadata toolbar to slap me. 

Again, if anyone has any ideas why ArcCatalog might have had problems translating the original metadata in the first place, or why this convoluted work around works, please let me know. 

Thx. 

Gavin

[GavinMcDade]

Update Part II:

Since I enjoy replying to myself, I'll do it once more:

Based on more testing, and having encountered additional feature classes which also crashed ArcCatalog during the Metadata Upgrade process, I've discovered that the "trick" to fixing the issue involves only the last of the aforementioned steps - that is, simply delete the offending dataset from SDE, then copy/paste it back in from any other SDE instance.  For whatever reason, when ArcCatalog freshly pastes the "new" dataset into SDE, the FGDC-to-ArcGIS metadata translation succeeds, whereas the former fails. 

Observations are welcome. 

Gavin