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

rmora_rollback
SYNOPSIS
rmora_rollback -s -p -t
[-o data|arch] [-v] [-w] [-f]
DESCRIPTION
The rmora_rollback command promotes the volumes of a database Virtual Copy back to their
base virtual volumes. Once promoted, the database virtual volumes will be exactly the same as
the volumes of the database Virtual Copy. If the Virtual Copy is the snapshot image of a standby
database, it can only be used to promote back to the standby database virtual volumes.
When rolling back from an online Virtual Copy, both datafile and archive log virtual volumes are
rolled back by default. Use the -o option to roll back only datafile virtual volumes or only archive
log virtual volumes.
When rolling back from an offline or datafile Virtual Copy, only datafile virtual volumes are rolled
back.
When rolling back from an archive log Virtual Copy, only archive log virtual volumes are rolled
back.
The following restrictions apply when rolling back a Virtual Copy:
•
The online redo logs and control files should not reside on the same virtual volumes used by
the datafiles and archive logs; if they do, they will be rolled back along with the datafile and
archive log virtual volumes. To avoid possible data corruption for other applications caused
by rolled-back volumes, the volumes used by the database should not be shared with other
applications.
•
The database instance must be CLOSED for this operation. If the database is an RAC database,
all RAC instances must be CLOSED.
•
The base (data file and/or archive log) virtual volumes and Virtual Copy volumes must not be
exported.
•
If the base virtual volumes are involved in a Remote Copy group you must use -f to promote
the Virtual Copies back to their base volumes.
•
The specified Virtual Copy must not be Orphaned since it does not belong to the original
parent volumes. The Virtual Copy is usable, but cannot be used for rmora_rollback.
•
The specified Virtual Copy must not be Stale since it resides on a Virtual Volume that is stale.
Recovery Manager for Oracle saves an ASCII control file and a binary control file for each created
Virtual Copy in its repository. After a rollback, you may need to restore the control file in order to
perform database recovery.
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 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
The Oracle SID of the database instance. For Real Application Cluster (RAC) database, an Oracle
SID of any RAC instance can be specified.
-p
96 Using the Recovery Manager Command Line Interface