Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

dbed_vmclonedb started at 2004-04-02 15:19:16
The snapshot status has been updated.
dbed_vmclonedb ended at 2004-04-02 15:19:42
In this example, file systems are mounted without recovering the clone database.
The clone database must be manually recovered before it can be used. This example
is for a clone created on a secondary host.
$ dbed_vmclonedb -S FLAS11r1 -o mountdb \
new_sid=test5cln,server_name=slias19 -f snap2 -r /tmp/test5cln
dbed_vmclonedb started at 2009-04-07 18:16:01
Editing remote_login_passwordfile in inittest5cln.ora.
All redo-log files found.
Altering instance_name parameter in inittest5cln.ora.
Altering instance_number parameter in inittest5cln.ora.
Altering thread parameter in inittest5cln.ora.
Database TEST5CLN (SID=test5cln) is in recovery mode.
If the database test5cln is recovered manually, you must run
dbed_vmclonedb -o update_status to change the snapshot status.
dbed_vmclonedb ended at 2009-04-07 18:17:58
The database is recovered manually.
The snapshot status (database_recovered) is updated for a clone database on a
secondary host after manual recovery has been completed.
$ /opt/VRTS/bin/dbed_vmclonedb \
-o update_status,new_sid=NEWPROD,server_name=orasvr -f snap2
dbed_vmclonedb started at 2004-04-09 23:34:01
The snapshot status has been updated.
dbed_vmclonedb ended at 2004-04-09 23:34:35
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:
■ ORACLE_SID is the name of the Oracle database used to create the
snapshot.
Using Database FlashSnap for backup and off-host processing
Cloning a database (dbed_vmclonedb)
282