Veritas Storage Foundation for Oracle 5.0 Administrator's Guide, HP-UX 11i v3, Second Edition, December 2008

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 -g snap_dg \
-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.
$ /opt/VRTS/bin/dbed_vmclonedb -S PROD -g SNAP_PRODdg \
-o mountdb,new_sid=NEWPROD,server_name=orasvr -f snap1 -r /clone
dbed_vmclonedb started at 2004-04-02 15:34:41
Mounting /clone/prod_ar on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_ar.
Mounting /clone/prod_db on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_db.
All redo-log files found.
Database NEWPROD (SID=NEWPROD) is in recovery mode.
If the database NEWPROD is recovered manually, you must run
dbed_vmclonedb -o update_status to change the snapshot status.
dbed_vmclonedb ended at 2004-04-02 15:34:59
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
dbed_vmclonedb started at 2004-04-02 15:19:16
The snapshot status has been updated.
dbed_vmclonedb ended at 2004-04-02 15:19:42
Using Database FlashSnap for backup and off-host processing
Cloning a database (dbed_vmclonedb)
270