Resynchronizing the Active and Standby Databases in a Warm Standby Application

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.

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
```
Suspend the Replication Server DSI connection to the active and standby databases:
```
suspend connection to dataserver.database
```
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
```
If the truncation point has not been moved, proceed to step 5. Otherwise, reinitialize the Replication Agent repository before you obtain a dump of the primary database contents. In the primary Replication Agent, execute:
```
ra_init force
go
```
Obtain a dump of the primary database contents following the instructions in your database documentation. If you use the Recovery Manager (RMAN) for Oracle, use the Oracle list backup command to obtain the last System Change Number (SCN) of the RMAN backup. Then, in Replication Agent, set this SCN as the value of lr_dump_marker:
```
lr_dump_marker oracle scn
```
Start the primary Replication Agent in resync mode and send a resync marker to Replication Server:
```
resume resync
go
```
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.
```
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.
```
Apply the dump of the primary database to the active database following the instructions in database documentation.
Move the truncation point to the end of the transaction log for the active database. In Replication Agent, execute:
```
pdb_xlog move_truncpt
go
```
Reinitialize Replication Agent repository based on the latest system data from the active database:
```
ra_init force
go
```
Start Replication Agent for the active database in resync mode with the init option. In Replication Agent, execute:
```
resume resync, init
```
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.
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 5 if the dump does not include database configuration information.
Resume DSI to the active and standby databases:
```
resume connection to data_server.database
```