You can use the RMU Recover command to apply the contents of an
.aij file to a restored copy of your database. Oracle RMU rolls
forward the transactions in the .aij file into the restored copy
of the database.
The RMU Recover command accepts a list of .aij or .oaij file
names. Unless you specify the Noautomatic qualifier, the RMU
Recover command attempts to automatically complete the recovery
operation by applying the journals currently associated with
the database in the current journal configuration if they are in
the recovery sequence. For example, if you specify the following
RMU Recover command, Oracle RMU not only recovers AIJ1, but also
AIJ2, AIJ3, and so on, for all journals in the recovery sequence:
$ RMU/RECOVER AIJ1
However, note that this automatic recovery feature means that
if you want to specify a termination condition, you must specify
the Until qualifier. Example 1 demonstrates how to specify a
termination condition with the Until qualifier.
If you are using extensible journals, you can also use the RMU
Backup After_Journal command to copy your database's .aij file to
tape, and truncate the original .aij file without shutting down
your database.
If you have backed up your .aij files (using the RMU Backup
After_Journal command), these .aij files are no longer part of
the current journal configuration and automatic recovery does
not take place because Oracle RMU does not know where to find
the .aij files. (There is one exception to this rule: if the only
.aij file that has been backed up is the first .aij file in the
recovery sequence, then automatic recovery occurs. You specify
the backed up .aij file on the Oracle RMU command line and Oracle
RMU can determine where the remaining on-disk .aij files reside.)
When automatic recover does not, or cannot occur, you must
specify the complete list of .aij files on the RMU Recover
command line to return your database to the desired state.
If your backup files were created using the Noquiet_Point
qualifier, you must provide the names of all the .aij files
in just one command. In addition, you must be careful to apply
these .aij files to the database in the order in which they
were created. Oracle RMU checks the validity of the journal
file entries against your database and applies only appropriate
transactions. If none of the transactions apply, you will receive
a warning message.
You can access your database for retrieval of data between
recovery steps, but you must not perform additional updates if
you want to perform more recovery steps.
If a system failure causes a recovery step to abort, you can
simply issue the RMU Recover command again. Oracle RMU scans
the .aij file until it finds the first transaction that has not
yet been applied to your restored database. Oracle RMU begins
recovery at that point.