VERITAS FlashSnap Point-In-Time-Copy Solutions Administrator's Guide

Chapter 5, Decision Support

Creating an Off-Host Replica Database

Note For a replica DB2 database, the database volume must be mounted in the same location

as on the primary host.

12. Copy any required log files from the primary host to the OHP host:

◆ For an Oracle database on the OHP host, copy the archived log files that were generated

while the database was in hot backup mode to the new database’s archived log directory

(for example, /rep/archlog).

◆ For a Sybase ASE database on the primary host, if you specified the for external

dump clause when you quiesced the database, use the following isql command as the

database administrator to dump the transaction log for the database:

dump transaction to dump_device with standby_access

Then copy the dumped transaction log to the appropriate database directory on the OHP

host.

13. As the database administrator, start the new database:

◆ If the replica DB2 database is not to be rolled forward, use the following commands to

start and recover it:

db2start

db2inidb database as snapshot

If the replica DB2 database is to be rolled forward (the primary must have been placed in

LOGRETAIN RECOVERY mode before the snapshot was taken), use the following

commands to start it, and put it in roll-forward pending state:

db2start

db2inidb database as standby

Obtain the latest log files from the primary database, and use the following command to

roll the replica database forward to the end of the logs:

db2 rollforward db database to end of logs

◆ For an Oracle database, use a script such as that shown in “Script to Complete, Recover

and Start Replica Oracle Database” on page 78. (This script also creates the control file for

the new database by executing the SQL script that you created using the procedure in

“Preparing a Replica Oracle Database” on page 81.)

◆ For a Sybase ASE database, use a script such as that shown in “Script to Start Replica

Sybase ASE Database” on page 80.

If you are using the warm standby method, specify the -q option to the dataserver

command. Use the following isql commands to load the dump of the transaction log and

put the database online:

load transaction from dump_device with standby_access