Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

To mount a database and recover it manually
1
Start and mount the clone database to allow manual database recovery:
$ /opt/VRTS/bin/dbed_vmclonedb -S ORACLE_SID \
-o mountdb,new_sid=new_sid,server_name=svr_name -f SNAPPLAN \
[-H ORACLE_HOME] [-r relocate_path]
2
Recover the database manually.
3
Update the snapshot status information for the clone database in the SFDB
repository:
$ /opt/VRTS/bin/dbed_vmclonedb \
-o update_status,new_sid=new_sid,server_name=svr_name \
-f SNAPPLAN [-r relocate_path]
In this example, file systems are mounted without bringing up the clone database.
The clone database must be manually created and recovered before it can be used.
This example is for a clone created on the same host as the primary database.
$ dbed_vmclonedb -S FLAS11r1 -o mountdb \
new_sid=test5cln,server_name=slias19 -f snap1 -r /tmp/test5cln
dbed_vmclonedb started at 2009-04-07 18:16:01
Editing remote_login_passwordfile in inittest5cln.ora.
All redo-log files found.
Altering instance_name parameter in inittest5cln.ora.
Altering instance_number parameter in inittest5cln.ora.
Altering thread parameter in inittest5cln.ora.
Database TEST5CLN (SID=test5cln) is in recovery mode.
If the database test5cln is recovered manually, you must run
dbed_vmclonedb -o update_status to change the snapshot status.
dbed_vmclonedb ended at 2009-04-07 18:17:58
The database is recovered manually using dbinitdb.
The database status (database_recovered) needs to be updated for a clone database
on the primary host after manual recovery has been completed.
$ /opt/VRTS/bin/dbed_vmclonedb \
-o update_status,new_sid=NEWPROD,server_name=orasvr -f snap1 \
-r /clone
281Using Database FlashSnap for backup and off-host processing
Cloning a database (dbed_vmclonedb)