Retrieving Data from the Primary Database Using the Adaptive Server dump and load, select, or bcp Commands

Use the Adaptive Server dump and load, select, or bcp commands and utilities to retrieve data from the primary database.

1. Verify that the entire replication system is working.
   See Replication Server Administration Guide Volume 2 > Verify and Monitor Replication Server.
2. Suspend updates to the data in the primary database by stopping client applications that generate transactions against the primary data.
3. Quiesce the replication system components involved with replicating data from the primary Replication Server to the replicate Replication Server.

   Use admin quiesce_force_rsi at the primary and replicate Replication Servers and at any intermediate Replication Servers.

4. Execute suspend log transfer for the primary database.
5. Take a snapshot of the subscription data from the primary database using a select statement or a database dump.
6. Execute define subscription at the replicate Replication Server.
7. Use check subscription at the primary and at the replicate Replication Servers to verify that the subscription has been defined. When the subscription status is DEFINED at both servers, continue to step 9.
8. Execute the activate subscription command, using the with suspension clause, at the replicate Replication Server.
9. Use check subscription at the primary and at the replicate Replication Server to verify that the subscription has been activated.When the subscription becomes active at the replicate Replication Server, the DSI connection to the replicate Replication Server is suspended.

   When the subscription status is ACTIVE at both servers, continue to step 11.

10. Execute resume log transfer from the primary database at the primary Replication Server.
11. Begin loading the snapshot data into the replicate database.
    Note: While you wait for the data to finish loading in the replicate database, you can continue with the next step.
12. Execute validate subscription at the replicate Replication Server to validate the subscription.
13. Use check subscription at the primary and at the replicate Replication Server to verify that the subscription status is VALID for both servers.
14. When the snapshot data has finished loading in the replicate database, execute resume connection to resume the connection to the replicate database.