Veritas Storage Foundation 5.1 SP1: Storage and Availability Management for Oracle (5900-1504, April 2011)

To shut down the clone database and unmount all snapshot file systems
◆
Use the dbed_vmclonedb command as follows:
$ /opt/VRTS/bin/dbed_vmclonedb -o umount,new_sid=NEWPROD,server_name=svr_name \
-f snap1 -r /clone
dbed_vmclonedb started at 2006-03-02 15:11:22
umounting /clone/prod_db
umounting /clone/arch
dbed_vmclonedb ended at 2006-03-02 15:11:47
In this example output, the clone database is shut down, file systems are
unmounted, and the snapshot disk group is deported for a clone on a
secondary host ( two node configuration).
$ /opt/VRTS/bin/dbed_vmclonedb -o umount,new_sid=NEWPROD,server_name=svr_name \
-f snap2
dbed_vmclonedb started at 2006-03-09 23:09:21
Umounting /prod_db
Umounting /arch
dbed_vmclonedb ended at 2006-03-09 23:09:50
In the following example output, the clone database is shutdown and the file
systems are unmounted for a clone created using mapped mounts.
dbed_vmclonedb -o umount,new_sid=NEWPROD,server_name=svr_name -f snap1
dbed_vmclonedb started at 2009-08-01 16:25:52
Umounting /tmp/dadst.
Umounting /tmp/ardst.
dbed_vmclonedb ended at 2009-08-01 16:25:57
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.
Using Database FlashSnap for backup and off-host processing
FlashSnap commands
188