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

Database Administrator user must exist on the backup server. In addition, permission on the Recovery
Manager for Oracle Installation and Repository directories must be changed appropriately.
OPTIONS
The following options are supported:
-s <oracle_sid>
The Oracle SID of the database instance. For Real Application Cluster (RAC) database, an Oracle
SID of any RAC instance can be specified.
-p <db_server>
The corresponding host name of the database server where the specified Oracle database instance
is running. The value of the database server 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 rmora_display command.
-n <clone_sid>
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 <clone_ora_home>
The Oracle home directory on the backup server. 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 control files of the clone database. The directories or ASM diskgroups must have
enough available space to hold new online redo logs and control files. 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 original database when creating a clone database. Otherwise,
the extra redo log multiplex location will be ignored.
-o ascii
Use an ascii control file which was saved in the Recovery Manager for Oracle repository to create
a clone database.
-o binary
Use a binary control file which was saved in the Recovery Manager for Oracle repository to create
a clone database.
-o for_backup
Use an binary control file which was saved in the Recovery Manager for Oracle repository to
create a clone database. The clone database is started in MOUNTED mode without recovery for
backup (RMAN) purpose. This option is equivalent to-o binary,norecovery. This option is
deprecated and will be removed in the future release.
-o recovery
Automatically recover the clone database using all available archivelogs that exist on the virtual
copy.
-o norecovery
Startup the clone database in mounted mode without recovery.
-v
Runs the command in verbose mode.
Recovery Manager Commands 67