HP 3PAR Application Software Suite for Oracle - Manual (Page 133)

6.19
Recovery Manager 3.0.3/3.0.4 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. The
primary database and the standby database cannot coexist on the same backup host.
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
The Oracle SID of the database instance. For Real Application Cluster (RAC) database, an
Oracle SID of any RAC instance can be specified.
-p
The corresponding host name of the database host where the specified Oracle database
instance is running. The value of the database host name must match the output of the
hostname command.
-t
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
The Oracle SID of the clone database. If this option is not specified, the clone database will
have the same Oracle SID as the original database. If this option is specified along with
-o binary|for_backup , the specified Oracle SID will be ignored.
-h
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.