Veritas Storage Foundation 5.0 for Oracle RAC Configuration Guide Extracts for HP Serviceguard Storage Management Suite, Second Edition, May 2008

Using FlashSnap for Backup and Recovery
Cloning a Database (dbed_vmclonedb)
Chapter 5
108
To mount a database and recover it manually:
1. Start and mount the clone database to allow manual database recovery:
$ /opt/VRTS/bin/dbed_vmclonedb -S ORACLE_SID -g snap_dg \
-o mountdb,new_sid=new_sid,server_name=server_name\
[,sfdbvol=vol_name] -f SNAPPLAN \
[-H ORACLE_HOME] [-r relocate_path]
2. Recover the database manually.
3. Update the snapshot status information for the clone database in the VxDBA
repository:
Table 5-9 Recover Database Notes
Prerequisites • You must be logged in as the Oracle database administrator.
• Before you can use the dbed_vmclonedb command, you must
validate a snapplan and create a snapshot. The volume snapshot
must contain the entire database.
• The system administrator must provide the database
administrator with access to the necessary volumes and mount
points.
• Before you can use the dbed_vmclonedb command with the -r
relocate_path option (which specifies the initial mount point for
the snapshot image), the system administrator must create the
mount point and then change the owner to the Oracle database
administrator.
•If SNAPSHOT_MODE is set to offline or instant, a two-host
configuration is required and -r relocate_path is not allowed.
• The Oracle database must have at least one mandatory archive
destination.
Usage Notes • The dbed_vmclonedb command can be used on the secondary
host.
• In a single-host configuration, -r relocate_path is required.
This command is also needed if the name of the clone database is
different than the primary database.
• The initialization parameters for the clone database are copied
from the primary database. This means that the clone database
takes up the same memory and machine resources as the
primary database. If you want to reduce the memory
requirements for the clone database, shut down the clone
database and then start it up again using a different init.ora file
that has reduced memory requirements. If the host where
dbed_vmclonedb is run has little available memory, you may not
be able to start up the clone database and the cloning operation
may fail.
•See the dbed_vmclonedb(1M) manual page for more information.