Veritas Storage Foundation 5.1 SP1 Advanced Features Administrator"s Guide (5900-1503, April 2011)

■ 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 the example.
See “Script to complete, recover and start a replica Oracle database”
on page 521.
(This script also creates the control file for the new database by executing
the SQL script that you created using the procedure in the section
preparing the replica Oracle database.)
See “About preparing a replica Oracle database” on page 525.
■ For a Sybase ASE database, use a script such as that shown in the example.
See “Script to start a replica Sybase ASE database” on page 523.
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
online database database_name for standby_access
If you are not using the warm standby method, use the following isql
command to recover the database, roll back any uncommitted transactions
to the time that the quiesce command was issued, and put the database
online:
online database database_name
Decision support
Creating an off-host replica database
190