The sequence of steps in the procedures for these scenarios documented in “Database resynchronization scenarios,” in Chapter 13, “Resynchronizing Oracle Replicate Databases” are incorrect:
Resynchronizing one or more replicate databases directly from a primary database
Resynchronizing using a third-party dump utility
Resynchronizing the active and standby databases in a warm standby application
The correct procedures are:
Resynchronizing directly from a primary database
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
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 Replication Agent, execute:
ra_init force go
Obtain a dump of the primary database contents. See your database documentation. If you use the Recovery Manager (RMAN) for Oracle, obtain the last System Change Number (SCN) of the RMAN backup using the Oracle list backup command. In Replication Agent, set this SCN as the value of lr_dump_marker:
lr_dump_marker oracle scn
Instruct Replication Agent to start in resync
mode and send a resync marker to Replication Server:
resume resync go
In the Replication Server system log, verify that DSI has received and accepted the resync marker from Replication Agent by looking for this message:
DSI for data_server.database received and processed Resync Database Marker. Waiting for Dump Marker.
After DSI processes the resync marker for the replicate database, you can apply the dump to the replicate database.
If you are resynchronizing multiple databases, verify
that the DSI connection for each of the databases you want to resynchronize
has accepted the resync marker.
Apply the dump of the primary database to the replicate database. See your database 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 using:
resume connection to data_server.database
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
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 Replication Agent, execute:
ra_init force go
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:
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 6 and set in step 7, 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
Resynchronizing the active and standby databases
when the warm standby environment is the replicate site
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. See your database documentation. If you use the Recovery Manager (RMAN) for Oracle, obtain the last System Change Number (SCN) of the RMAN backup using the Oracle list backup command. In Replication Agent, set this SCN as the value of lr_dump_marker:
lr_dump_marker oracle scn
Instruct the primary Replication Agent to start
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. See your 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
Instruct Replication Agent for the active database
to start 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
