Select to view content in your preferred language

Problem with replica creation

1796
5
09-12-2013 06:51 AM
DonnaRiebe
Occasional Contributor
Greetings,

I am having problems creating a new replica based on my version on the sde database on my local machine.  Our main sde database is located in the capital and editing across the distance has been slow, so having a replica locally has worked well.  We just recently upgraded to 10.1, but the sde database is still at 9.3.  My problems started when I tried syncing my replica to my version on the sde database for the first time after we were upgraded.  My replica was corrupted and I have been unable to create a replacement. 

I have tried multiple machines, all the data, 1 feature class only , both two-way and check-out replicas, but the process crashes almost immediately and I get a 000582 error when using my version.  Also there is an error message stating that the version was not found.  Although I can connect to and view the data in my version with no problem in both ArcGIS and ArcCatalog.

I do seem to be able to create a checkout replica from DEFAULT from the sde database, just not my version.  Any help on this would be appreciated.

My computer ArcGIS 10.1 sp1
Win XP pro sp3

Donna Riebe
Montana DNRC
0 Kudos
5 Replies
WilliamCraft
MVP Alum
I may be able to help you, but I need to make a few assumptions and/or ask some questions.  Are you using SQL Server or Oracle?  It sounds like you're interested in creating a two-way replica but I cannot be sure.  I am going to use Oracle as my basis for some of the answers for the time being.  

First, let's make sure that the previous replica version is removed from the geodatabases before trying to create a new one.  Keep in mind that whenever your unregister a replica (i.e., delete its version) from a geodatabase, it should be done while connected as the replica owner and not necessarily the SDE user.  Open ArcCatalog and connect to both of your geodatabases as the replica owner, then right-click them and expand the Distributed Geodatabase menu, and look at the Manage Replicas item.  It should be grayed out... if not, then click it to see the list of replicas.  Right click each one in the list and choose Unregister. 

Next, go ahead and issue the following query to your TWO geodatabases using a tool like Oracle SQL Developer (otherwise known as the parent and child geodatabases especially if you're using a 1-way):

SELECT * FROM SDE.VERSIONS
WHERE NAME LIKE '%SYNC_SEND%'

If any versions are returned, you'll need to delete them using ArcSDE command line as shown below.  Substitute the SYNC_SEND version name with one from the result set above.  Replica versions are hidden and can't be seen in ArcCatalog... only directly from the GDB using SQL.  Replica versions always begin with SYNC_SEND. 

sdeversion -o delete -V SYNC_SEND_X_X -u <replica_owner> -p password -i esri_sde -s DBSERVER -D db_name


This should get you to the point of starting over with a clean slate.  You'll need to re-create / register the replica again.  To do this, make sure the connection you use for ArcSDE contains the intended replica owner account as well as the intended transactional version. 

Once the replica is created and registered in both geodatabases, make some edits to the parent version of the replica and then try to sync the changes via ArcMap.  This can actually be done with the "connected" tools or the disconnected tools.  Check the ReplicaLog.dat file at the following location (assumes Windows 2008 R2): C:\users\<your_domain_user_account>\AppData\Local\Temp.  Open the file with a text editor and see if there are any errors throughout.  If not, go back to ArcCatalog's "Manage Replica" GUI from the Distributed Geodatabase menu, right click your replica in the list, and choose View Log.  If your results say "ERROR" then right click the line item in the list and view the error report. 

Let me know the results and we can try to troubleshoot this together further.
0 Kudos
DonnaRiebe
Occasional Contributor
I may be able to help you, but I need to make a few assumptions and/or ask some questions.  Are you using SQL Server or Oracle?  .



I am using SQL express on my computer, the main database in Helena is Sql Server.

I
t sounds like you're interested in creating a two-way replica but I cannot be sure.  I am going to use Oracle as my basis for some of the answers for the time being.  
  ...Snip other helpful stuff...  .


Yes, I am trying to do a two way replica.  And to be honest (and as a warning 🙂  ), my sql server skills are pretty minimal, but I am pretty decent at following directions.

Thanks for the help.
0 Kudos
CherylCleghorn
Esri Contributor
Please do not blindly unregister your replicas or delete those replica versions especially if you have functional replicas. If you are having trouble with one replica there is no need to unregister all replicas. Your best bet is to contact Support Services. They would be able to troubleshoot with you.

Regards
Cheryl
0 Kudos
WilliamCraft
MVP Alum
Please do not blindly unregister your replicas or delete those replica versions especially if you have functional replicas. If you are having trouble with one replica there is no need to unregister all replicas. Your best bet is to contact Support Services. They would be able to troubleshoot with you.

Regards
Cheryl


Donna, a point of clarification that I'll make based on Cheryl's remarks.  The way your original post is written suggests that you have one and only one replica that is registered with the geodatabase.  Therefore, it was my intention that the instructions I provided to initially troubleshoot the issue involved cleaning out the replica and its related sync send verion(s) that may not be working properly.  I was hoping to get you back to a good starting point so that you could try again to create and register your replica.  I don't believe you have other replicas registered besides the one you described, so I don't think you would be "blindly unregistering" replicas that are otherwise working correctly but I could be wrong. 

Let me know when you have more information to report once you have walked through the steps I described.  Of course, you could also open a support ticket but that is certainly your decision.  Good luck.
0 Kudos
DonnaRiebe
Occasional Contributor
After struggling with this for some time, the simple answer seemed to be that while we had upgraded our DESKTOPS to 10.1, the SDE database was still at 9.3.  That simply wouldn't work.  So after IT finally updated the geodatabase AND we figured out which file it kept asking for, the new replica I created syncs back and forth without a hitch.

Thanks for everyones input.

Donna
0 Kudos