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

To start the clone database
◆
Use the dbed_vmclonedb command as follows:
$ /opt/VRTS/bin/dbed_vmclonedb -S ORACLE_SID -g snap_dg \
-o restartdb,new_sid=new_sid,server_name=svr_name -f SNAPPLAN \
[-H ORACLE_HOME] [-r relocate_path]
In this example, the clone database is re-started on the same host as the
primary database (a single-host configuration).
$ /opt/VRTS/bin/dbed_vmclonedb -S PROD -g SNAP_PRODdg \
-o restartdb,new_sid=NEWPROD,server_name=orasvr -f snap1 -r /clone
dbed_vmclonedb started at 2004-04-02 15:14:49
Mounting /clone/prod_db on
/dev/vx/dsk/SNAP_PRODdg/SNAP_prod_db.
Oracle instance NEWPROD successfully started.
dbed_vmclonedb ended at 2004-04-02 15:15:19
In this example, the clone database is re-started on the secondary host (a
two-host configuration).
$ /opt/VRTS/bin/dbed_vmclonedb -S PROD -g SNAP_PRODdg \
-o restartdb,new_sid=NEWPROD,server_name=orasvr \
-f snap2
dbed_vmclonedb started at 2003-04-09 23:03:40
Mounting /clone/arch on
/dev/vx/dsk/SNAP_PRODdg/SNAP_arch.
Mounting /clone/prod_db on
/dev/vx/dsk/SNAP_PRODdg/SNAP_prod_db.
Oracle instance NEWPROD successfully started.
dbed_vmclonedb ended at 2003-04-09 23:04:50
Recreating Oracle tempfiles
After a clone database is created and opened, the tempfiles are added if they were
residing on the snapshot volumes. If the tempfiles were not residing on the same
file systems as the datafiles, dbed_vmsnap does not include the underlying volumes
in the snapshot. In this situation, dbed_vmclonedb issues a warning message and
you can then recreate any needed tempfiles on the clone database as described
in the following procedure.
Using Database FlashSnap for backup and off-host processing
Cloning a database (dbed_vmclonedb)
274