I spoke with someone at ESRI technical support about a workflow I currently use where I have to unregister any child replicas in order to compress my database to state_id=0. Unregistering and deleting these replicas allows this to succeed. The problem is that I then need to recreate my child replicas with the original name so my mxd links don't break. However, creating a new geodatabase in SQL Server Express 2005 won't allow me to name them the original name. So I'm forced to create replicas with a new name every time, and then I have to open each mxd and repair the source which is very time consuming.
The person I talked with at ESRI said I could unregister the replica, compress, and then re-register the replica. I didn't think this was possible and I can't figure out how. Any ideas?
You shouldn't have to unregister your replicas in order to compress to a state of 0. After you reconcile/post your versions and delete them, synchronize all your replicas. After you synchronize all replicas make sure no users are connected and then compress your database. This should successfully compress to a state of 0.
You shouldn't have to unregister your replicas in order to compress to a state of 0. After you reconcile/post your versions and delete them, synchronize all your replicas. After you synchronize all replicas make sure no users are connected and then compress your database. This should successfully compress to a state of 0.
Thanks for your reply! I've been made aware of two troubleshooting items necessary to compress to State_ID=0. Going through both procedures has been the ONLY way my db will compress to State_ID=0.
It would be nice if the first of these two articles wasn't necessary, but performing both of these steps has been the only way. (PS - compressing always "succeeds" but will not result in State_ID=0 unless I go through both methods...)
Version 9.2 on Oracle 10g. (soon to be Version 10 but until then...) I've got 3 two-way replicas that users of an ArcEngine application utilize (these replicas are pSDE on Sql Express 2005) And the only versions I ever have are when I make edits to data in SDE. I'm not directly editing sde.default ever.
I tested with ArcSDE 10, but I it should be the same for 9.2. I was able to compress my database to a state of 0 without unregistering any of my replicas. Here are the steps I took:
1. Reconciled and posted each child version to the SDE.Defeault version 2. Deleted the child versions 3. Synchronized each replica 4. Disconnected all users from the geodatabse 5. Ran a compress
Can you try the same steps and see if you can reproduce?
I sure will - I'll report back what I find - hopefully today.
But in the meantime another question: Unregistering a replica is as good as deleting a replica because you can't synchronize changes once a replica has been unregistered. Which goes back to my initial question in the thread: can you reregister a replica?
If you cannot, any thoughts on a suitable workaround? My workaround has been to unregister the replicas and delete them, and recreate them - but the issue is when I recreate them I can't name them to their original name...
This WORKED. 🙂 It's possible that the reason I was told to unregister my replicas was because when I performed the troubleshooting items from the articles from above, I did have to deal with orphaned versions / replicas (i.e. SYNC_SEND_<replica id>) and ESRI tech support was just trying to help me get a clean slate. I don't have orphaned versions now which may be the difference in a complete compress without having to unregister replicas.
So this changes my workflow for the better and speeds things up. Thanks for your time!
