Use this procedure to coordinate resynchronization after you dump the primary database using a third-party dump utility, such asa disk snapshot.
Third-party tools do not interact as closely with the primary database as native database dump utilities. If your third-party tool does not record anything in the primary database transaction log that Replication Agent can use to generate a dump database marker, generate your own dump database markers to complete the resynchronization process. See your third-party tool documentation.
Resynchronizing after using a third-party utility
to create a dump
Stop replication processing by Replication Agent. Do not alter the truncation point. In Replication Agent, execute:
suspend
Suspend the Replication Server DSI connection to the replicate 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 Replication Agent:
resume connection to data_server.database skip to resync marker
Obtain a dump of the primary database contents using the third-party dump utility.
Determine the dump point based on information from the primary database when you took the dump, or information from the third-party tool. With a third-party tool, you are responsible for determining the dump point. For example, if you are using a disk replication tool, you can temporarily halt activity at the primary database to eliminate transactions in progress from the disk snapshot, and then use the “end of transaction log” point as the dump database marker.
Execute the stored procedure on the primary database for Replication Agent to mark the end of the dump position that you obtained in step 5:
lr_dump_marker oracle scn
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
Replication Agent automatically generates a dump database marker at a time based on the end of dump position that you obtained in step 5 and set in step 6, and sends the dump database marker to Replication Server.
Verify that DSI has received and accepted the resync marker from 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.
Apply the dump of the primary database from the third-party tool to the replicate database. See your database and third-party tool documentation.
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.
After you apply the dump to the replicate database, resume DSI:
resume connection to data_server.database
