Select to view content in your preferred language

Unable to Save Edits

2804
3
05-29-2013 08:29 PM
AgiHOIRE
Emerging Contributor
I have never experience this since I started using ArcGIS v. 10. I have a brand new polygon generated in ArcCatalogue then dragged into map data frame in Arcmap to edit and draw. All goes well until I hit 'Save Edits' and the new drawn feature completely disappears. The whole featureclass edits cannot be saved and also ends up corrupt and unusable when previewed in ArcCatalogue and when displayed in arcmap. I'm wondering if anyone out there has enountered this problem and has a clue in solving it.

This has frustrated the hell out of me and have lost data so appreciate anyone who can provide me some answers.
Thanks in advance!
Tags (2)
0 Kudos
3 Replies
MarkYoung
Regular Contributor
Right click over the feature class, click the indexes tab then recalculate the spatial index. Then try your edits and save.
0 Kudos
AgiHOIRE
Emerging Contributor
Thanks a lot Mark! Will try this out. However I have long suspected and believe I started enountering this issue when somehow began Edit Versioning. Still trying to figure out how to revert to doing unversioned edits.

Appreciate your help.
Agi
0 Kudos
MarkYoung
Regular Contributor
Hi Agi,
Are you using the correct version?
Have you been using versioned editing for a while? If so it sounds like the user you connect to the sde as has run out of table space. I had the exact same issue unable to save edits. When you version a feature class (you version the entire database not just one feature class!) you create delta tables which store the adds and deletes in the state tree. Its from these tables the undo and redo actions can be enabled. Every time you make an edit, delete or add a new feature it writes to these additional tables which uses more space on the database. Eventually, if not maintained you will run out of space giving rise to the error - unable to save edits. What you have to do is compress these delta tables to free up space. You could also ask your dba (if you are lucky enough to have one!) to increase the table space of whatever user you are connecting to the database as.

Take caution before you compress. Ensure all edits have been reconciled and posted back to the default and delete any other versions. You can compress the state tree by using either command line syntax or tools in ArcCatalog. If possible there should be no connections to the database. Every connection means a lock to that table and a locked table will not have its delta tables compressed. To find out how many connections there are open a command prompt on the machine running Sde open a command prompt (start>run and type cmd) and type the following;

sdemon -o status

That will tell you how many connections it is accepting. Ideally you want this to say 0 connections.

Take a look at the following link on how to compress the state tree.

http://support.esri.com/fr/knowledgebase/techarticles/detail/29160

I
f you wish to return to unversioned editing then you need to unregister your feature class(es) as versioned. Search for unregister in Catalog/Toolbox and select your feature class(es). Now that you have unversioned your feature class you need to change your editing settings in ArcMap. In ArcMap click Editor>Options then the Versioning tab and un-tick 'Edit a version of the database with option to undo and redo'. But as that last statement reads be wary, you are unable to undo any mistakes.

If you wish to continue to use versioned editing then schedule a regular compress

Hope all that makes sense.

Mark
0 Kudos