Error Unable To Compress State Tree
Contents |
Early Adopter Program ArcGIS Ideas Esri Support Services ArcGIS Blogs ArcGIS Code sdegdbrepair Sharing Product Life Cycles Manage Cases Request Case
Sdegdbrepair Python
Start Chat Back to results Print Share Is This Content Helpful? Search on arcsde command line tools GeoNet Submit to ArcGIS Ideas Error: Unable to compress state tree Error Message This problem is addressed in ArcGIS 8.1 Service Pack 1. See the Related Information section to download this pack.Using DB2, compression fails when the SDE.STATES table has 202 states. Cause An error inside the DB_sp_states_def_delete function causes the compression to fail when SDE.STATES table has exactly 202 states (also fails for 402, 602, 200xN+2, etc.). Solution or Workaround Download Service Pack 1. Related Information Download ArcGIS 8.1 Service Pack 1 Created: 5/5/2016 Last Modified: 5/5/2016 Article ID: 000004090 Software: ArcGIS - ArcEditor 8.1 ArcGIS - ArcInfo 8.1 ArcSDE 8.1 Is This Content Helpful? Is This Content Helpful? Yes No We're glad to know this article was helpful. How can we make this better? Submit Contact our Support Team Request Case Start Chat Questions or issues with the site? Send Feedback Contact Support USA +1-888-377-4575 Name Email URL Please rate your online support experience with Esri's Support website.* Poor Below Satisified Satisfied Above Satisfied Excellent What issues are you having with the site? How can we improve? Submit Feedback sent successfully. Error while sending mail. Loading
<{ORACLE10G|ORACLE11G|SQLSERVER|DB2|DB2ZOS|INFORMIX|POSTGRESQL}> [-H
Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://gis.stackexchange.com/questions/114223/how-to-explain-why-a-particular-arcsde-state-does-not-compress of this site About Us Learn more about Stack Overflow the company Business http://prog3.com/sbdm/blog/linghe301/article/details/7331992 Learn more about hiring developers or posting ads with us Geographic Information Systems Questions Tags Users Badges Unanswered Ask Question _ Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. Join them; it only takes a minute: Sign up Here's how it works: Anybody error unable can ask a question Anybody can answer The best answers are voted up and rise to the top How to explain why a particular ArcSDE state does not compress? up vote 0 down vote favorite 2 I am maintaining an ArcSDE database and would like to avoid killing connections to ArcSDE in order to run the compress operation. Our versioning workflow is very simple. Everyone error unable to edits the DEFAULT version directly. I know that it is not possible to compress to state 0 without reconciling and removing connections but we do not need to compress to state 0. All our applications are accessing SDE via ESRI software or an API which can access the DEFAULT version so our users/scripts should have access to all the data all the time. Having said that I am constantly monitoring the states that remain uncompressed and sometimes I cannot explain why a specific state would not be merged with state 0. I know that if there is branching in the state tree due to current edit sessions, some of those states cannot be removed. Same is the case if you have named versions that have not been reconciled. Also if users have locks on particular states, those states will not be blown away. For this reason I kill processes that are older than 1 day. But what if I have a linear state tree and a couple of states that do not have state locks on them do not get removed? Why might this be? What other factors influence which states get remo
benefits Hadoop hero will - and Hadoop 10 anniversary birthday [] a blog expert Award - Windows PowerShell practical guide to probation Solution method of ArcGIS version compression (Compress) newspaper unique constraint ORA-00001: label Oracle10gPostgreSQLSqlserverOracle11gInformixTable 09:18 2012-05-02 2395 people read comment(1) Collection report Classification: ArcSDE(193) Author similar articleX performance optimization(53) Author similar articleX Geodatabase(58) Author similar articleX Copyright statement: This article is the original article for the blogger, without permission may not be reproduced. In using ArcGIS version compression, often appear such problem, this version is compressed to a waiting process, if there is a problem, we difficult to determine the root of the problem where, below we will focus on several typical compression error to see how to solve? -o compress -u SDE -p sdeversion SDE ArcSDE Server Repair Utility ESRI ------------------------------------------------------------ State tree: Are you sure Compress (Y/N): y Underlying DBMS error Error: (-51). Unable to compress state tree. Error: Unique constraint ORA-00001: (GDB.A40_PK) violated Error information from the above we can easily know is caused by repeated a40 the table's primary key, then this problem we should how to modify it, if the table structure or knowledge database must be familiar with the person of ArcSDE may directly from the database level up to solve the problem of the, so if these are not familiar with, we can solve, because ArcSDE provides a command to check and repair these errors. C:\Users\Administrator>sdegdbrepair ArcSDE 10 Repair Administration Utility Repair ----------------------------------------------------- For sdegdbrepair: Usage -? -h Diagnose_tables -d {ORACLE10G|ORACLE11G|SQLSERVER|DB2|DB2