Summary of Database Initialization Methods

Consider the issues for each of the initialization methods and the role of these markers.

Issues in Initializing the Standby Database

Issue

Use dump and load with “dump marker”

Use dump and load without “dump marker”

Use bcp

Use mount

Working with client applications.

Use if you can not suspend transaction processing for client applications.

Use if you can suspend transaction processing for client applications.

Use if you can suspend transaction processing for client applications.

When does Replication Server begin replicating into the standby database?

Replication Server starts replicating into the standby database from the first dump marker after the enable replication marker.

Replication Server starts replicating into the standby database from the enable replication marker.

Replication Server starts replicating into the standby database from the enable replication marker.

Creating maintenance user login names and making sure all user IDs match.

Add the login name for the standby database maintenance user in both the active Adaptive Server and the standby Adaptive Server, and ensure that the server user’s IDs match.

(You create login names in the active Adaptive Server because using dump and load to initialize the standby database with data from the active database overrides any previous contents of the standby database with the contents of the active database.)

When you add the standby database, Sybase Central or rs_init adds the maintenance user login name and user in the standby Adaptive Server and the standby database.

Add the login name for the standby database maintenance user in both the active and standby Adaptive Servers. Ensure that the server user’s IDs match. (You create login names in the active Adaptive Server because using mount to initialize the standby database with data from the active database overrides any previous contents of the standby database with the contents of the active database.)

Initializing standby database.

Use dump and load to transfer data from the active database to the standby database.

You can use database dumps and/or transaction dumps.

Use bcp to copy each replicated table from the active database to the standby database.

Use quiesce database ... to manifest_file and mount database to transfer data from the active database to the standby database.

Active database connection state.

The connection to the active database does not change.

Replication Server suspends the connection to the active database.

Replication Server suspends the connection to the active database.

Resuming connections.

Resume connection to the standby database.

Resume connections to the active and standby databases; resume transaction processing in the active database.

Resume connections to the active and standby database; resume transaction processing in the active database.