I think i went to long between reconciling and posting

[RandallClark2]

So i think i made a mistake and went to long with reconciling my QA version with its parent DEFAULT version.

I say this because I started the reconcile process on a friday afternoon and its now Monday and it is still going on, luckily no errors. 

This reconcile is taking place outside of an edit session and is being handled in ArcCatalog via Administer Geodatabase 

So my question is what do i do? 

Do  i just let it keep running till it finishes and learn my lesson.

Or is there something else i can do?

Thanks 

[George_Thompson]

Hi Randall,

You can stop the process if you need to.

You cannot use the Undo operation to undo a reconcile operation. Any time you try to undo a reconcile operation, you will get an error message because Undo is not a supported operation. To undo a reconcile, you must exit your edit session without saving changes.

A quick tour of reconciling a version—ArcGIS Help | ArcGIS for Desktop 

[ChrisDonohue__GISP]

George Thompson 

If I can tag onto this, what would be the best/safest way to stop the process if it seems the Reconcile is running endlessly/will never finish?  My concern is if there would be any locks SDE may keep in place, plus potential data corruption (hopefully unfounded concerns).  Is there a recommended way to terminate the Reconcile process?

Chris Donohue, GISP

[George_Thompson]

Hi Chris - 

It has been a while since I have been on the technical side, but I believe that most of the reconcile is done in memory in the edit session. If you stopped the edit session and closed the MXD, it should clean up any items and not leave any orphans.

Let's see of anyone else has other ideas.

[RandallClark2]

Hi George that's good to know, but once i cancel it what can i do?

If it is taking this long to reconcile, wont it take as long as next time?

Also this is not happening in an edit session but through Geodatabase Administration in ArcCatalog

[George_Thompson]

You are correct it will have to be run and complete at some point.

You could try it via the edit session and see if the behavior is different.

Other option is to reach out to https://community.esri.com/groups/technical-support?sr=search&searchId=958f396c-b634-4627-b0d0-b2832...‌ and the Geodatabase team to have them review the behavior.

Side question: Where there any other processes running over the weekend on the geodatabase?

[RandallClark2]

No no other process running.

Luckily so far its not locking up anything so i can still work.

I guess i will just let it run for a few more days... 

edit: QA version is locked up.

[George_Thompson]

I would open a support case for this. It is possible that something is out of whack that needs a specialist to look at.

I think that 3 days is probably too long to reconcile a version, but I could be wrong.

[RobWilkes]

Hi Randall,

I am currently in the exact same situation. I was wondering if you were ever able to find a solution? I have been posting to default for 4.5 days now. Did you just let it run until it finished or was there something nefarious going on in the background?

[RandallClark2]

Something nefarious but im still not sure what.

I do know it was related to a child version. I believe it that was generated when a map was taken off line for use in Collector.

I do know when i went and deleted those versions everything was working fine.

So best guess is a version that was created by taking a map offline was preventing stuff from reconciling and posting so i would check and see if you have any versions like that.