Database resynchronization scenario

The following section describes a scenario containing the procedure you must follow to resynchronize databases. After completing the procedure, the primary and replicate databases are transactionally consistent.

To execute the procedure, you must:

Be a replication system administrator
Have an existing replication environment that is running successfully
Have methods and processes available to copy data from the primary database to the replicate

See the Replication Server Reference Manual for full command syntax.

You can only use this procedure for Adaptive Server.

Resynchronizing a replicate database

In this procedure, you do not have to stop replication processing by RepAgent.

Suspend the Replication Server DSI connection to the database:
```
suspend connection to dataserver.database
```
Instruct Replication Server to remove data from the replicate database outbound queue and wait for a resync marker from the primary database:
```
resume connection to data_server.database skip to 
resync marker
```
Ensure that there are no open transactions in system log, and then in the primary database, generate the resync marker manually by executing rs_marker with resync database:
```
execute rs_marker ‘resync database’
```
In the Replication Server system log, verify that DSI has received and accepted the resync marker by looking for this message:
```
DSI for data_server.database received and processed
Resync Database Marker. Waiting for Dump Marker.
```
Obtain a dump of the primary database contents. See the Adaptive Server documentation for instructions. Adaptive Server generates a dump database marker automatically.
Apply the dump of the primary database to the replicate database. See the Adaptive Server documentation for instructions.
See the Replication Server system log to verify that Replication Server has processed the dump database marker by looking for this message:
```
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.
After you apply the dump to the replicate database, resume DSI:
```
resume connection to data_server.database
```