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

will be then taken out of backup mode. An archive log switch will be performed before virtual
copies of archive log virtual volumes are created.
•
If the specified database instance is a physical standby database, the database will be
temporarily taken out of managed recovery mode before the virtual copy of the datafile virtual
volumes is created. The database will then be put back into the original managed recovery
mode.
A datafile virtual copy alone cannot be used to restore and recover the database. An archive log
virtual copy can be used in conjunction with an online virtual copy to simulate an incremental
backup.
Once created, the virtual copy can be mounted on the backup server for off-host processing purposes
such as backup and database cloning. If the virtual copy will be backed up using Oracle RMAN,
the primary database (not the standby database) must be registered with the Oracle Recovery
Catalog Database.
To use the rmora_create command, the Oracle database structure must satisfy the following
requirements:
•
The database must be running in archive log mode and automatic archival must be enabled
in order to create an online, datafile, or archive log virtual copy.
•
If archive log mode is enabled, the datafiles and archive logs must reside on separate 3PAR
virtual volumes.
•
The online redo logs and control files should not reside on the same 3PAR virtual volumes
used by the datafiles and archive logs to avoid being restored when using Recovery Manager
for Oracle Rollback feature. However, the online redo logs and control files can share the
same 3PAR virtual volumes.
•
If the database files reside on Symantec VxVM volumes, the datafiles and archive logs must
reside on separate VxVM disk groups. The online redo logs and control files should reside on
separate VxVM volumes used by the datafiles and archive logs.
•
If you use HP LVM Volume Manager, the Oracle datafiles and archive logs must reside on
separate LVM volume groups. In addition, online redo logs and control files must not reside
on LVM volume groups that are used by Oracle datafiles and archive logs. However, the
online redo logs and control files can reside on the same LVM volume group.
•
If the Oracle database is an ASM-managed database, the Oracle datafiles and archive logs
must reside on separate ASM disk groups. The online redo logs and control files should not
reside on the same ASM disk groups used by the datafiles and archive logs to avoid being
restored when using the Recovery Manager Rollback feature. In addition, ASM disk groups
should not be shared between different databases.
•
If the Oracle database is an RAC database, all RAC instances must share the same archive
log destinations (i.e., the same cluster file system or the same ASM disk groups).
•
If the database files are symbolic links pointing to actual files and the links do not reside on
the same file systems as the actual files, only the actual files are backed up. Otherwise, only
the first links and the actual files are backed up; intermediate links will not be backed up.
You must run this command as a super user or Oracle owner user from the backup server. To allow
the Oracle Database Administrator (Oracle owner) to run this command, an identical Oracle
Database Administrator user must exist on 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>
Recovery Manager Commands 63