Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

■ new_sid specifies the ORACLE_SID for the clone database.
■ server_name=svr_name specifies the server on which the primary database
resides.
■ SNAPPLAN is the name of the snapplan file.
■ ORACLE_HOME is the ORACLE_HOME setting for the ORACLE_SID
database.
■ relocate_path is the name of the initial mount point for the snapshot
image.
Note: When cloning a database on a secondary host, ensure that PRIMARY_HOST
and SECONDARY_HOST parameters in the snapplan file are different.
When the -o recoverdb option is used with dbed_vmclonedb, the clone database
is recovered automatically using all available archive logs. If the -o recoverdb
option is not used, you can perform point-in-time recovery manually.
In the following example, a clone of the primary database is automatically created
on the same host as the primary database.
$ /opt/VRTS/bin/dbed_vmclonedb -S PROD \
-o recoverdb,new_sid=NEWPROD,server_name=orasvr -f snap1 -r /clone
dbed_vmclonedb started at 2009-05-26 09:29:39
Editing remote_login_passwordfile in initclone1.ora.
All redo-log files found.
Altering instance_name parameter in initclone1.ora.
Altering instance_number parameter in initclone1.ora.
Altering thread parameter in initclone1.ora.
Database CLONE1 (SID=clone1) is running.
dbed_vmclonedb ended at 2009-05-26 09:32:16
In the following example, a clone of the primary database is automatically created
on a secondary host.
$ /opt/VRTS/bin/dbed_vmclonedb -S PROD \
-o recoverdb,new_sid=NEWPROD,server_name=orasvr -f snap2
dbed_vmclonedb started at 2009-04-15 05:57:51
Editing remote_login_passwordfile in initclone1.ora.
All redo-log files found.
Altering instance_name parameter in initclone1.ora.
Altering instance_number parameter in initclone1.ora.
283Using Database FlashSnap for backup and off-host processing
Cloning a database (dbed_vmclonedb)