topic Re: Re-use Replica Names in Geodatabase Questions

Re-use Replica Names

JoeBorgione — Tue, 03 Oct 2017 15:07:56 GMT

Is there a way to clear the entries (where ever they are) of Replica Names? Out of the box if you try to re-use a Replica Name (even if you unregister it on both ends) you'll get an error to the effect of 'That name is already in the master database"....

Re: Re-use Replica Names

Asrujit_SenGupta — Tue, 03 Oct 2017 15:10:28 GMT

You should be able to reuse the Replica name...

Can you elaborate on the message you get when trying to do so...

Re: Re-use Replica Names

JoeBorgione — Tue, 03 Oct 2017 15:37:37 GMT

Sure- Here's a screen shot when I try to reuse the name Checkout1. It says the version associated with it still exists, but it gets deleted when you sync the check out with the reconcile and post option.

Re: Re-use Replica Names

JoeBorgione — Tue, 03 Oct 2017 15:42:56 GMT

And here is the one that squawks about the Replica...

Re: Re-use Replica Names

JoeBorgione — Tue, 03 Oct 2017 16:10:11 GMT

If you don't set a name, the default (MyCheckOut) gets incremented the next time you try to use it...

Re: Re-use Replica Names

LeonS — Tue, 03 Oct 2017 16:24:02 GMT

I've run into that if I "Unregister" a replica in Catalog and then try to reuse that replica name in ArcMap prior to closing out Catalog. If you haven't already, I would try closing out everything to ensure there is no connection to you geodatabase then try it again.

If that doesn't work there might be some orphaned records in your geodatabase. You can check the GDB_ITEMS table to see if there are any references to the old replica, though I would probably go the Esri support route before touching anything in there!

Re: Re-use Replica Names

Asrujit_SenGupta — Tue, 03 Oct 2017 16:31:02 GMT

Take a look at the Versions table in the Database. Most probably you have that version there.

Re: Re-use Replica Names

JoeBorgione — Tue, 03 Oct 2017 16:40:14 GMT

Good catch Leon! That did it.

asengupta-esristaff‌ - your comment below is spot on; I've been experimenting with a check out replica work flow and managed to write one to a wrong location, hence the version error.