For 2 days running, the daily versioned DB compress hangs. Generally takes 3-5 minutes to complete. Ideas on why this might be happening and how to fix / avoid? TIA.
Mary
Hi Mary,
Do you have any locks on your geodatabase? You may want to give this tool a try:
https://community.esri.com/docs/DOC-9914-compress-geodatabase-tool
No, no locks on the DB. I always check just before beginning the compress.
Is there a benefit to using a tool rather than simply R-clicking on the DB and selection ‘Compress’?
Yes, this tool will ensure there are no locks, no users connected, and no users can connect to the geodatabase when the compress is occurring. It will also reconcile/post all versions to ensure that you are compressing to a state of 0.
We regularly to what we term the full compress to state 0 several times a year.
None of this answers the question of what happened during these 2 compresses, and what can be done to avoid / fix it so it does not recur in future. Ideas?
How was this resolved? I had to stop compression after taking 10 hours.
Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
