Configuring Database Resynchronization

Set up Oracle databases resynchronization.

1. Stop replication processing by suspending Replication Agent.
2. Place Replication Server in resync mode. While in resync mode, Replication Server skips transactions and purges replication data from replication queues in anticipation of the replicate database being repopulated from a dump taken from the primary database or trusted source.
3. Obtain a dump from the primary database.
4. Restart Replication Agent and send a resync database marker to Replication Server to indicate that a resynchronization effort is in progress.

   When Replication Server detects a dump marker that indicates the completion of the primary database dump, Replication Server stops skipping transactions and can determine which transactions to apply to the replicate database.

5. Apply the dump to the replicate database.
6. Reinitialize the replicate database.
7. Resume replication.

• Instructing Replication Server to Skip Transactions
  Use the skip to resync parameter with the resume connection command to instruct Replication Server to skip transactions in the DSI outbound queue for the specified replicate database until Replication Server receives and acknowledges a dump database marker sent by Replication Agent.
• Send the Resync Database Marker to Replication Server
  You can configure or instruct Replication Agent for Oracle to send a resync database marker to Replication Server to indicate that a resynchronization effort is in progress.
• Obtain a Dump of the Database
  Use any dump utility to obtain a dump of the database.
• Send the Dump Database Marker to Replication Server
  When the Data Server Interface thread (DSI) is in resync mode after you resume DSI using skip to resync marker, and you restart Replication Agent in resync mode, the dump database marker received after the resync database marker suspends DSI and removes any existing resynchronization state for that DSI connection.
• Monitor DSI Thread Information
  Use the admin who command to provide information on DSI during database resynchronization.
• Apply the Dump to a Database to be Resynchronized
  You can load the primary database dump to the replicate database only after you see messages in the system log.
• Reinitializing the Replicate Database
  After you apply the dump from the primary database or dump source to the replicate database, reinitialize the replicate database to restore users, tables, and permissions that the dump removed.