Synchronization failed (w option "Register Existing Data" in Create Replica Wizard)

[tongkimongki]

Hi,

I am having problem with synchronisation when I choose "Register Existing Data Only" in "Create Replica Wizard". The object just wont synched (ie : the new object doesnt get copied into the feature class in the replica database). There is no error when i do the synchronization...

But, the synchronisation is successfull when i choose "Data" in "Create Replica Wizard". Both, the new FC and the data in it, got synched...

Synch, with option "Register Existing Data Only" in Create Replica Wiz,  doesnt  work for both FC that are created using cold backup nor with the FC that are created using option "Data" in Create Replica Wiz.

The child geodatabase is created using cold backup (copying the tablesapces into new server). My environment: Win Server 2003 enterprise, Arcsde 9.2 sp 6, Oracle 10gr2.

Any help will be appreciated..

thanks

[CherylCleghorn]

It appear that you are having trouble creating the replica. Replicas can only be synchronized after they have been created.

Creating replicas with the 'Register existing data ' option does not copy the data to the relative replica during the creation process.

Please contact esri Support Services so that we can assist you with the workflow and checking to see that all prerequisites have been satisfied on the child.

Thanks
Cheryl

[tongkimongki]

Hi,

BTW, The replica creation is successful... the problem is with the synchronization process... 😞

Here are what I did :

1. I created a featureclass, lets call it FC1, in master database. Then i edit FC1, add new objects then save. Then i click "Create Replica Wizard" with option "Data". Then i click "Synchronize". The new featureclass,FC1, and its objects are copied to the child database during synchronize.

2.  I do editing on FC1 again on master database and save it. Then i click Create Replica with option "Register Existing Data Only" (as its already been created in step 1), then click "synchronize". The new object are not copied into FC1 in the child database.

The master and child database are exactly the same. I cold-back-up it. The child database is functioning perfectly, i can do editing,query,analysis, etc...
 
thanks

[CherylCleghorn]

You seem to be mixing up the two processes. Initially, create replica with the data option does copy the data over to the child so there is no need to synchronize immediately after the replica is created.

Once the replica is created, it will continue to exist until you unregister it; there is no need to try to create it again after performing edits. Just perform your edits and use the synchronize button to send the changes to the child replica i.e. eliminate the 'intermediate' step of creating replica with the register existing data option.

Hope this helps

Cheryl

[tongkimongki]

hi..

i got it working. actually, there was no error...

what i did  were : edit (updating) one of the attribute and do sycnhronisation again. surprisingly, The newly updated attribute is updated on the replica database. then i repeat with editing without updating attribute (just add new objects), do sycnhronisation again and the newly added objects appeared on the replica database !

though its solved, i still dont know why the synch failed before..

cheers 😄

[CherylCleghorn]

Glad you have it working now.

The reason why it did not work before was at step 2 where you a) added a feature and then b) created the replica with the 'register existing data option'. With this workflow, when you create the replica the data is assumed to be the same in both geodatabases and new edits are determined from this point onward. Because the feature was only added in the master before the replica was created, the master and child were not identical.

Hope this helps.

Regards
Cheryl