Converts any of the following versions (or any of the mandatory
updates to these versions) of Oracle Rdb databases to an Oracle
Rdb release 7.2 database:
o Version 7.0
o Version 7.1
See the Oracle Rdb Installation and Configuration Guide for the
proper backup procedure prior to installing a new release of
Oracle Rdb and converting databases.
NOTE
The following are important issues to consider when you
convert a database:
o A database must be backed up immediately following an
Oracle RMU convert operation.
A database converted using the RMU Convert command may
not be recoverable if a full database backup is not made
immediately after the convert operation completes. If you
attempt to restore a database using a backup file created
prior to the conversion, the database may be left in an
unrecoverable state.
o If after-image journaling is enabled when you issue
the Convert command, Oracle RMU disables after-image
journaling during the convert operation and then does
one of the following, depending on the type of .aij file
or files being employed when the Convert command was
issued:
- If an extensible .aij file was being used, Oracle RMU
creates a new journal for the converted database and
enables after-image journaling.
- If fixed-size .aij files were being used, Oracle RMU
activates the next available fixed-size journal and
enables after-image journaling. If another fixed-
size journal is not available, journaling remains
disabled.
Use only the .aij file (or files) created or activated
during or after the convert operation together with the
backup file you created immediately after the convert
operation to restore and recover your database. Any .aij
files created prior to the Convert operation cannot be
used to recover the converted database.
If you issue an RMU Convert command with the Rollback
qualifier, Oracle RMU disables after-image journaling
and returns the message: RMU-I-CANTENAAIJ. Oracle
Corporation recommends that you back up the database and
enable after-image journaling when the convert operation
completes.
o Growth of the RDB$SYSTEM storage area is normal during
a convert operation. You must be sure that there is
sufficient disk space for the new metadata and the
converted metadata.
During a convert operation Oracle RMU makes an upgraded
copy of the metadata. If the convert operation fails,
the old metadata is available for rolling back. If
you specify the Nocommit qualifier, both copies of
the metadata exist at the same time (to allow a manual
rollback operation). If you specify the Commit qualifier,
the old metadata is deleted once the convert operation
completes successfully.
Read the Description help entry under this command carefully for
important information on converting single-file and multifile
databases.
Additional Information:
explode
extract