Synchronizing connected replicas
This topic applies to ArcEditor and ArcInfo only.
Use the Synchronize wizard to synchronize changes between replicas.
There are two ways to open the wizard, through the Distributed Geodatabase toolbar or through the context menu in the Catalog tree.
To open the Synchronize wizard from the toolbar, first open the Distributed Geodatabase toolbar in ArcMap if it is not already open. Click Customize, point to Toolbars, and click Distributed Geodatabase. To activate the Synchronize wizard, click the Synchronize button on the Distributed Geodatabase toolbar.Note:The Synchronize wizard supports both local and remote geodatabases. Remote geodatabases are accessed in ArcMap through map services that have the geodata access capability enabled.Tip:To get more information on Synchronization, click the About Getting Replica Changes button.
To open the Synchronize wizard from the Catalog tree, right-click the geodatabase or the geodata service with which you want to synchronize, point to Distributed Geodatabase, then click Synchronize Changes.
On the first panel of the Synchronize wizard, choose the replica that you want to synchronize.
Once selected, the dialog box will show the replica type.
Browse for the local or remote geodatabase containing that replica.
Tip:If the connection information for the relative replica is stored with the replica, it appears automatically, and you do not need to browse.
Choose the direction in which you would like to send changes.
If the replica is check out/check in or one way, then you can only choose the appropriate direction. If the replica is two way, you can send changes from geodatabase 1 to geodatabase 2, from 2 to 1, or in both directions.
- Click Next.
- For checkout replicas, there is an option to reconcile and post with the parent version upon synchronization. For two-way and one-way replicas, this is always checked on.
Next, choose to define conflicts By Object or By Attribute.
Defining conflicts by object detects conflicts by row, while defining them by attribute detects conflicts by column.
- Choose how you want conflicts resolved: in favor of geodatabase 1, in favor of geodatabase 2, or manually.
- Click Finish.