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

Altering thread parameter in initclone1.ora.
Database CLONE1 (SID=clone1) is in recovery mode.
If the database clone1 is recovered manually, you must run
dbed_vmclonedb -o update_status to change the snapshot status.
dbed_vmclonedb ended at 2010-06-22 00:13:19
The database status (database_recovered) needs to be updated for a clone database
on the primary host after manual recovery has been completed.
$ /opt/VRTS/bin/dbed_vmclonedb -o update_status,\
new_sid=NEWPROD,server_name=svr_name -f snap1 -r /clone
dbed_vmclonedb started at 2006-03-02 15:35:16
The snapshot status has been updated.
dbed_vmclonedb ended at 2006-03-02 15:35:42
To clone the database automatically
◆
Use the dbed_vmclonedb command as follows:
$ /opt/VRTS/bin/dbed_vmclonedb -S ORACLE_SID \
-o recoverdb,new_sid=new_sid,server_name=svr_name -f SNAPPLAN \
[-H ORACLE_HOME] [-r relocate_path]
Where:
Represents the name of the Oracle database used to create the
snapshot.
ORACLE_SID
Specifies the ORACLE_SID for the clone database.new_sid
Specifies the server name as svr_name.server_name
Represents the name of the snapplan file.SNAPPLAN
Represents the ORACLE_HOME setting for the ORACLE_SID
database.
ORACLE_HOME
Represents the name of the initial mount point for the snapshot
image.
relocate_path
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
185Using Database FlashSnap for backup and off-host processing
FlashSnap commands