Retrieving Data from the Primary Database Using the Adaptive Server mount Command

Use the mount command to retrieve data from the primary database.

Prerequisites

You can use this method only if you are using Adaptive Server version 12.5.1 or later, and your primary and replicate databases are identical.

Task

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

Use admin quiesce_for_rsi at the primary and replicate Replication Servers and any intermediate Replication Servers.
Execute the Adaptive Server command quiesce database tag_name hold db_name list [for external dump] to manifest_file [with override]] to generate the manifest file.
See the Adaptive Server Enterprise Reference Manual.
Take a snapshot of the subscription data from the primary database by creating a data dump of both the database and log devices.
You can create a data dump using utilities such as tar or zip, or the UNIX dd command.
Use mount database to begin loading the snapshot data into the replicate database.
Resolve the mismatch of user information between the master database and the loaded user database.
Use rs_init to add the replicate database to the replication system if it is not already there.
Execute define subscription at the replicate Replication Server.
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 11.
Execute activate subscription at the replicate Replication Server.
Use check subscription at the primary and at the replicate Replication Server to verify that the subscription has been activated. When the subscription status is ACTIVE at both servers, continue to step 13.
Execute quiesce release to resume updates to the primary data.
Execute validate subscription at the replicate Replication Server.
Use check subscription at the primary and at the replicate Replication Server to verify that the subscription is VALID at both servers.

When you have completed this procedure, the subscription is created, the replicate data is consistent with the primary data, and replication is active.