Resynchronizing if There is No Support for the Resync Database Marker

Coordinate resynchronization if the RepAgent or the primary database have not been updated to support automatic generation of a resync marker.

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

   suspend connection to dataserver.database

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

   resume connection to data_server.database skip to 
   resync marker

3. Ensure that there are no open transactions in system log, and then in the primary database, manually generate the resync marker:

   execute rs_marker ‘resync database’

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

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

5. Obtain a dump of the primary database contents.
   Adaptive Server automatically generates a dump database marker.See Adaptive Server Enterprise Reference Manual: Commands > Commands > dump database.
6. 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.

7. Apply the dump of the primary database to the replicate database. See Adaptive Server Enterprise Reference Manual: Commands > Commands > load database.
8. After you apply the dump to the replicate database, resume DSI:

   resume connection to data_server.database