Step 1: Select "Rebuild current extent"
Step 2: Operation failed.
Is it just the Rebuild Extent that fails or does the Validate fail too? Also making sure that the UN is added to the map and just out of curiosity are you running this on default version? The Underlying DBMS error is quite generic, any chance you can look at the logs on debug mode. I find that's where most direct causes will be visible. Side Note: You mentioned corrupt geometry - The rebuild extent tool only repairs topology inconsistencies not the underlying geometry. If you are having issues specifically with geomteries then worth investigating those first.
Well… this is on a SQLite database we are using the flush out the thousands of dirty areas present in our data. The error "Underlying DBMS Error [Success]" occurs in a variety of circumstances, including on attempting to delete an offending feature.
And its not limited to occasions when the Attribute Table is open, as is mentioned in some bug.
Which is really a pain, since the particular error raised — like coincident junction features — is usually masking many other other errors that we can't resolve.
Is it for every feature or just one of them? Would you be able to share a database containing an undeletable feature?
This looks like a bug, please keep a copy of the broken database around and log a case.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
