Resynchronizing After Using a Third-Party Utility to Create a Dump

  1. Stop replication processing by Replication Agent. Do not alter the truncation point. In Replication Agent, execute:
    suspend
  2. Suspend the Replication Server DSI connection to the replicate database:
    suspend connection to dataserver.database
  3. 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
  4. 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
  5. Use the third-party utility to obtain a dump of the primary database contents.
  6. Determine the dump point based on information from the primary database when you took the dump, or information from the third-party utility. With a third-party utility, 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 in-progress transactions from the disk snapshot, and then use the “end of transaction log” point as the dump database marker.
  7. To mark the end of the dump position that you obtained in step 5, execute the stored procedure on the primary database for Replication Agent:
    lr_dump_marker oracle scn
  8. Restart Replication Agent 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.

  9. 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.
  10. Apply the dump of the primary database from the third-party tool to the replicate database, following the instructions in the database and third-party utility documentation.
  11. 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.

  12. After you apply the dump to the replicate database, resume DSI:
    resume connection to data_server.database