Resynchronizing the active and standby databases in a warm standby application

Use this procedure to resynchronize the active and standby databases in a warm standby environment, when the warm standby pair is the replicate site for a single primary database. In this scenario, the active, standby, and primary databases are Oracle databases.

1. Stop replication processing by both the primary database Replication Agent and the warm standby active database Replication Agent. Do not alter the truncation point. In Replication Agent, execute:

   suspend
   

2. Suspend the Replication Server DSI connection to the active and standby databases:

   suspend connection to dataserver.database
   

3. Instruct Replication Server to remove data from the outbound queue of the active and standby databases, 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. See your database documentation. If you use Recovery Manager (RMAN) for Oracle, obtain the last System Change Number (SCN) of the RMAN backup. In the primary Replication Agent, configure this SCN as the value of lr_dump_marker :

   lr_dump_marker oracle scn
   

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

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

     resume resync
     

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

     ra_init force
     go
     resume resync
     go
     

6. Verify that DSI for the active database has received and accepted the resync marker from the primary database Replication Agent by looking for this message in the Replication Server system log:

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

7. Verify that the Replication Server DSI for the active database has processed the dump database marker by looking for this message from the active database 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.
   

8. Apply the dump of the primary database to the active database. See your database documentation.

9. Move the truncation point to the end of the transaction log for the active database. In Replication Agent, execute:

   pdb_xlog move_truncpt
   go
   

10. Reinitialize Replication Agent repository based on the latest system data from the active database:

    ra_init force
    go
    

11. Instruct Replication Agent for the active database to start in resync mode with the init option. In Replication Agent, execute:.

    resume resync, init
    

12. Verify that DSI for the standby database has received and accepted the resync marker from the active database Replication Agent by looking for this message In the Replication Server system log:

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

    When Replication Server receives and processes the resync database with init marker, the DSI connection suspends.

13. Obtain a dump of the active database contents and apply the dump to the standby database. You can also apply the dump of the primary database from step 4 if the dump does not include database configuration infomation.

14. Resume DSI to the active and standby databases:

    resume connection to data_server.database