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

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 (same-node configuration).
$ /opt/VRTS/bin/dbed_vmclonedb -S FLAS11r2 \
-o restartdb,new_sid=clone1,server_name=motmot \
-f snap1 -r /cudb
dbed_vmclonedb started at 2010-06-21 23:54:04
Oracle instance clone1 successfully started.
dbed_vmclonedb ended at 2010-06-21 23:55:19
In this example, the clone database is re-started on the secondary host (two
node configuration).
$ /opt/VRTS/bindbed_vmclonedb -S FLAS11r2 \
-o restartdb,new_sid=clone1,server_name=motmot \
-f snap1
dbed_vmclonedb started at 2010-06-17 00:43:42
Oracle instance clone1 successfully started.
dbed_vmclonedb ended at 2010-06-17 00:44:59
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.
189Using Database FlashSnap for backup and off-host processing
FlashSnap commands