Software Suite for Oracle Instruction Manual

6.16
Command
Recovery Manager for Oracle User’s Guide
When creating a clone database for backup (RMAN) purposes, the database is started in
MOUNTED mode using the binary controlfile from the repository without recovering the
database. This can be achieved by using -o for_backup or -o binary,norecovery option.
A clone database can be created with or without automatic recovery (applying archivelogs
from the virtual copy) using –o recovery or -o norecovery option, if recovery is chosen, the
clone database is open with reset log, otherwise, the clone database is in mounted status.
You must run this command as a super user from the backup host. To allow the Oracle
Database Administrator (Oracle Owner) to run this command, an identical Oracle Database
Administrator user must exist on the backup host. In addition, permission on the 3PAR
Recovery Manager Installation and Repository directories must be changed appropriately.
OPTIONS
The following options are supported:
■ -s <oracle_sid> - The instance SID of the primary database. For an RAC database, any
instance SID can be specified.
■ -p <primary_host> - The corresponding host name of the primary host where the
specified Oracle database instance is running. The value of the primary host name must
match the output of the
hostname command.
■ -t <timestamp> - The timestamp of a virtual copy. It is also the name of the virtual copy.
The virtual copy name can be obtained using the
vcdba_display command.
■ -n <clone_sid> - The new Oracle SID for the clone database. If this option is omitted or
is used with the -o for_backup option, the clone database will have the same
ORACLE_SID as the primary database. If creating a clone database with the -o binary
option, the new Oracle SID will be ignored.
■ -h <clone_oracle_home> - The Oracle home directory on the backup host. If specified,
this value will be used instead of the value of the parameter ORACLE_HOME_BACKUP in the
configuration file.
■ -d <loc> - A comma-separated list of directories or ASM diskgroups (for multiplexing) to
store the new online redologs and controlfiles of the clone database. The directories or
ASM diskgroups must have enough available space to hold new online redo logs and
controlfiles. Users who run this command must have write permission to this directory or
directories. The number of multiplex redo log locations must be equal to or less than the
primary database when creating a clone database. Otherwise, the extra redo log multiplex
location will be ignored.