nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcCatalog: "Failed to process XML dara, possibly due to data corruption"

EdwardBlair

My machine running and Oracle SDE database recently crashed. On starting it back up I try to open any of the feature classes and get the message:

"Failed to edit the selected objects(s).
Failed to process XML data, possibly due to corruption"

Can this be repaired? Any suggestions would be much appreciated.

Thanks,
Ed

Trouver plus de publications taguées avec

Accepted answers

All comments

WilliamCraft

Anytime, Ed. I am only sorry I couldn't help to resolve the issue. Enjoy your weekend!

EdwardBlair

Yep. Quite sure. Was working with it up to the point of the crash.

I really, really appreciate your help with this. Am thinking restoring from backup will be the best course as well.

Thanks again,
Ed

WilliamCraft

Obvious question... but I need to ask... are you certain that this feature class was behaving correctly before the server crash? If the answer is yes, then it looks like you should restore from a backup.

EdwardBlair

Tried, and it errored in the feature class Export process with the message "Cannot create output <feature class>"

Sure looks like the Feature Dataset definition is corrupted in some way and the feature classes can't get a reference back to get their spatial reference.

Ed

WilliamCraft

Do you get the same error if you try to export the feature dataset with the corrupt feature classes to a file geodatabase?

EdwardBlair

My next step would be to re-load this database from back-up, so deleting rows from the LOCKS tables is OK with me. So it did.

However, when connecting to ArcCatalog I appear to be in the same boat. Classes in the "corrupt" database still error on opening with the message "Failed to process XML..."

Feature classes in other datasets behave OK.

Ed

WilliamCraft

Is this a test or production database? If it's a test database, make a complete backup and then let's try deleting the rows in the locks tables if you're comfortable doing that. If it's a production database, then your safest bet is to use caution and open a support ticket with Esri.

Assuming this is a test database and you're comfortable with taking a full backup first, run the following in SQLplus after restarting your database once again (ensuring no ArcGIS client connections exist):

TRUNCATE TABLE SDE.STATE_LOCKS;
TRUNCATE TABLE SDE.TABLE_LOCKS;

Then try to view the "bad" feature class(es) again in ArcCatalog.

** Once again, I only suggest this on a test database after a full backup has been taken. **

EdwardBlair

Clicking on the "Locks" tab actually throws the error message "Failed to process XML data, possibly due to data corruption".

On dismissing the error message the list is empty -- if that means anything.

WilliamCraft

Ok, thanks. Make a connection to your geodatabase now using ArcCatalog as the SDE user. Once connected, right click the connection, open the Administration menu and pick Administer Geodatabase. When the Admin UI opens, select the Locks tab and check if any locks are listed. If they are (other than yours), right click then and pick Disconnect User. Let me know the results.

EdwardBlair

I did the shutdown and start-up (through I usually do this through the Sevices applet) so it took me a bit.

Queries returned the same results as before.

Ed

WilliamCraft

Ok, let's do this... restart your Oracle database:

SQLPLUS SYS/password@DATABASENAME as sysdba
SHUTDOWN IMMEDIATE
STARTUP

Once the database is back up, make sure there are no ArcGIS connections from any clients including services. You need to be absolutely sure there are no user or service connections. Then re-run those 4 queries against the locks tables and let me know if the results are different.

EdwardBlair

Here are the query results:

SQL> select * from sde.table_locks;

    SDE_ID REGISTRATION_ID L LOCK_TIME
---------- --------------- - ---------
    447312             162 S 08-MAY-14
    447312             163 S 08-MAY-14
    447312             164 S 08-MAY-14
    447312             165 S 08-MAY-14
    447312             166 S 08-MAY-14
    447312             167 S 08-MAY-14
    447312             168 S 08-MAY-14
    447312             169 S 08-MAY-14
    447312             170 S 08-MAY-14
    447312             171 S 08-MAY-14
    447312             172 S 08-MAY-14
   <Many more rows>

110 rows selected.

SQL> select * from sde.layer_locks;

no rows selected

SQL> select * from sde.object_locks;

no rows selected

SQL> select * from sde.state_locks;

    SDE_ID   STATE_ID A L LOCK_TIME
---------- ---------- - - ---------
    447312     149542 N S 08-MAY-14

EdwardBlair

Thanks for jumping in..

Oracle 11.2.0.1
ArcGIS 10.1 SP1
Everything's on one machine.. Windows 7

The query returns one row.

MAJOR 10
MINOR 1
etc.

Ed

WilliamCraft

Now that you've posted the additional info, can you disconnect all sessions from your geodatabase and then run the following queries in SQLplus and post the results?

SELECT * FROM SDE.SDE_TABLE_LOCKS;
SELECT * FROM SDE.SDE_LAYER_LOCKS;
SELECT * FROM SDE.SDE_OBJECT_LOCKS;
SELECT * FROM SDE.SDE_STATE_LOCKS;

WilliamCraft

Hi again, Ed. I'm not sure if I'll be much help on this one, but let's see if we can at least try to get some more error reporting. A few questions first though...

Which version of Oracle?
Which version is the geodatabase?
Which version of ArcGIS Desktop?
Which operating systems are involved?

One quick thing I'd like to verify is if you can actually query the tables in Oracle after making a SQLplus connection. Open up a command prompt (I'm going to assume you're on Windows) and type the following; then let me know if the query returns a result:

SQLPLUS username/password@DATABASENAME
SELECT * FROM SDE.VERSION;

EdwardBlair

A little more information on this.

There are four datasets in the database. Only one of them has this problem. The other four seem to be OK. The dataset with the problem had a participating feature class present in an ArcMap session when the computer crashed.

Ed

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.