Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

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 \
-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 \
-o restartdb,new_sid=NEWPROD,server_name=orasvr -f snap1 -r /clone
dbed_vmclonedb started at 2009-04-15 06:04:10
Oracle instance clone1 successfully started.
dbed_vmclonedb ended at 2009-04-15 06:07:14
In this example, the clone database is re-started on the secondary host (a
two-host configuration).
$ /opt/VRTS/bin/dbed_vmclonedb -S PROD \
-o restartdb,new_sid=NEWPROD,server_name=orasvr \
-f snap2
dbed_vmclonedb started at 2009-04-15 06:04:10
Oracle instance clone1 successfully started.
dbed_vmclonedb ended at 2009-04-15 06:07:14
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
285Using Database FlashSnap for backup and off-host processing
Cloning a database (dbed_vmclonedb)