Compress can potentially delete non-leaf states

Last Published: January 11, 2021


Compress has the potential for deleting non-leaf states while compress is executing, if users are editing simultaneously. When compress reads the state_lineages and states table into memory, there is potential where a new state’s predecessor/primary state can be mistakenly deleted.

ArcSDE software, including the application server, command tools, and SDK with C and Java APIs, was deprecated at ArcGIS 10.2.2 and is no longer distributed. 


The compress operation reads the state_lineages and states table into memory as one of the first steps it performs when compressing the ArcSDE instance. If users are editing while the compress operation reads these tables into memory, there is a possibility the compress operation can delete a state which it believes is a leaf state that is not referenced by any versions, does not have a state lock and is not a primary state of any other states.


The compress operation and the delete state operation now validates when an individual state is deleted that the state is not referenced by any other states (meaning the state being deleted is not a primary state).

This fix has been addressed in the ArcSDE 9.1 General Update Patch 2. 

    Article ID:000008614

    Receive notifications and find solutions for new or common issues

    Get summarized answers and video solutions from our new AI chatbot.

    Download the Esri Support App

    Related Information

    Discover more on this topic

    Get help from ArcGIS experts

    Contact technical support

    Download the Esri Support App

    Go to download options