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

To mount a database and recover it manually
1
Start and mount the clone database to allow manual database recovery:
dbed_vmclonedb started at 2010-04-29 02:21:57
Editing remote_login_passwordfile in initclons1.ora.
All redo-log files found.
Altering instance_name parameter in initclons1.ora.
Altering instance_number parameter in initclons1.ora.
Altering thread parameter in initclons1.ora.
Database CLONS1 (SID=clons1) is in recovery mode.
If the database clons1 is recovered manually, you must run
dbed_vmclonedb -o update_status to change the snapshot status.
dbed_vmclonedb ended at 2010-04-29 02:25:28
2
Follow the Oracle recovery procedure to recover the database manually.
3
Update the snapshot status information for the clone database in the SFDB
repository:
The output displayed is :
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
Example: Mounting the file systems without bringing up the clone database
In this example, file systems are mounted without bringing up the clone database.
The clone database must be manually created and recovered before it can be used.
This example is for a clone created on the same host as the primary database.
Note: You must issue commands as an Oracle database administrator in the
following procedure.
$ /opt/VRTS/bin/dbed_vmclonedb -S FLAS11r2 \
-o mountdb,new_sid=clone1,server_name=motmot -f snap1 \
-r /cudb
dbed_vmclonedb started at 2010-06-22 00:11:45
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.
Using Database FlashSnap for backup and off-host processing
FlashSnap commands
184