Veritas Storage Foundation™ 5.0.1 for Oracle RAC Installation, Configuration, and Administrator's Guide Extracts for the HP Serviceguard Storage Management Suite on HP-UX 11i v3

dbed_vmclonedb started at 2006-03-02 15:34:41
Mounting /clone/prod_db on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_db.
Mounting /clone/prod_ar on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_ar.
All redo-log files found.
Altering instance_name paramter in initabc.ora.
Altering instance_number paramter in initabc.ora.
Altering thread paramter in initabc.ora.Starting automatic database recovery.
Database NEWPROD (SID=NEWPROD) is in recovery mode.
If the database NEWPROD is recovered manually, you must run
dbed_vmclonedb -o update_status to change the snapshot status.
dbed_vmclonedb ended at 2006-03-02 15:34:59
2. The database is recovered manually using dbinitdb command.
3. 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=host1 -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
Example: Mounting the file systems without recovering the clone database
1. 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.
# /opt/VRTS/bin/dbed_vmclonedb -S -g SNAP_PRODdg -o
mountdb,new_sid=NEWPROD,vxdbavol=SNAP_arch -f snap2
dbed_vmclonedb started at 2006-03-09 23:26:50
Mounting /clone/arch on /dev/vx/dsk/SNAP_PRODdg/SNAP_arch.
Mounting /clone/prod_db on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_db.
All redo-log files found.
Altering instance_name paramter in initabc.ora.
Altering instance_number paramter in initabc.ora.
Altering thread paramter in initabc.ora.
Starting automatic database recovery.
Database NEWPROD (SID=NEWPROD) is in recovery mode.
If the database NEWPROD is recovered manually, you must run
dbed_vmclonedb -o update_status to change the snapshot status.
dbed_vmclonedb ended at 2006-03-09 23:27:17
2. The database is recovered manually.
3. 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 -f
snap2
dbed_vmclonedb started at 2006-03-09 23:34:01
The snapshot status has been updated.
dbed_vmclonedb ended at 2006-03-09 23:34:35
78 Using FlashSnap for Backup and Recovery