Resynchronizing one or more replicate databases directly from a primary database

Use this procedure to resynchronize one or multiple replicate databases from a single primary database. This procedure, with minor variations, allows you to:

• Repopulate the replicate database when the replication latency between primary and replicate databases is such that to recover a database using replication is not feasible, and reporting based on the replicate data may not be practical because of the latency.

• Repopulate the replicate database with trusted data from the primary database.

• Coordinate resynchronization when the primary database is the source for multiple replicate databases.

1. Stop replication processing by Replication Agent. Do not alter the truncation point. In Replication Agent, execute:

   suspend
   

2. Suspend the Replication Server DSI connection to the replicate database:

   suspend connection to dataserver.database
   

3. Instruct Replication Server to remove data from the replicate database outbound queue and wait for a resync marker from the primary database Replication Agent:

   resume connection to data_server.database skip to 
   resync marker
   

4. Obtain a dump of the primary database contents. If you use Oracle Recovery Manager (RMAN) tool, obtain the last System Change Number (SCN) of the RMAN backup using the Oracle list backup command. In Replication Agent, set this SCN as the value of lr_dump_marker:

   lr_dump_marker oracle scn
   

5. Instruct Replication Agent to start in resync mode and send a resync marker to Replication Server:

   • If the truncation point has not been moved from its original position, execute this command in Replication Agent:

     resume resync
     

   • If the truncation point has been moved from its original position, you must reinitialize the Replication Agent repository before you send the resync marker. In the Replication Agent, execute:

     ra_init force
     go
     resume resync
     go
     

6. In the Replication Server system log, verify that DSI has received and accepted the resync marker from Replication Agent by looking for this message:

   DSI for data_server.database received and processed
   Resync Database Marker. Waiting for Dump Marker.
   

   After DSI processes the resync marker for the replicate database, you can apply the dump to the replicate database.

   If you are resynchronizing multiple databases, verify that the DSI connection for each of the databases you want to resynchronize has accepted the resync marker.

7. Apply the dump of the primary database to the replicate database. See your database documentation.

8. Verify that Replication Server has processed the dump database marker by looking for this message in the Replication Server system log:

   DSI for data_server.database received and processed
   Dump Marker. DSI is now suspended. Resume after database has been reloaded.
   

   When Replication Server receives the dump marker, the DSI connection automatically suspends.

9. After you apply the dump to the replicate database, resume DSI using:

   resume connection to data_server.database