VERITAS Storage Foundation 4.1 Oracle Administrator's Guide

Chapter 10, Using Database FlashSnap for Backup and Off-Host Processing
Prerelease 8 September 2005, 8:55am Cloning a Database (dbed_vmclonedb)
247
Example
In this example, the clone database is shut down, file systems are unmounted, and the snapshot disk
group is deported for a clone on a secondary host (a two-host configuration).
$ /opt/VRTS/bin/dbed_vmclonedb -o umount,new_sid=NEWPROD \
-f snap2
dbed_vmclonedb started at 2004-04-09 23:09:21
NOTICE: Umounting /clone/arch.
NOTICE: Umounting /clone/prod_db.
dbed_vmclonedb ended at 2004-04-09 23:09:50
Restarting a Clone Database
If the clone database is down as a result of using dbed_vmclonedb -o umount or rebooting
the system, you can restart it with the -o restartdb option.
Note This option can only be used when a clone database is created successfully. If the clone
database is recovered manually, -o update_status must be run to update the status
before -o restartdb will work.
▼ 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 -f SNAPPLAN [-H ORACLE_HOME] \
[-r relocate_path]
For information on restarting the clone database using the GUI, see “Using the VERITAS Storage
Foundation for Oracle Graphical User Interface” on page 265.
Example
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 -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.
Mounting /clone/prod_ar on
/dev/vx/dsk/SNAP_PRODdg/SNAP_prod_ar.
Oracle instance NEWPROD successfully started.
dbed_vmclonedb ended at 2004-04-02 15:15:19