Example 1
The first command in the following example converts an Oracle Rdb
release 7.0 database with an extensible .aij file to an Oracle
Rdb release 7.2 database. Because the Nocommit qualifier is
specified in the first command, you can roll back the converted
database (the Oracle Rdb release 7.2 database) to the original
Oracle Rdb release 7.0 database.
After-image journaling is disabled while the database is being
converted. After the database is converted, a new extensible .aij
file is created and after-image journaling is enabled again. Note
that .aij files are version-specific. You should perform a full
backup operation after a conversion because the old version and
the new version of the .aij file are incompatible.
In the second command, the converted database is rolled back to
the original database.
$RMU/CONVERT/CONFIRM/NOCOMMIT MF_PERSONNEL.RDB
%RMU-I-RMUTXT_000, Executing RMU for Oracle Rdb V7.2-00
Are you satisfied with your backup of
DISK1:[TESTS]MF_PERSONNEL.RDB;1
and your backup of any associated .aij files [N]? Y
%RMU-I-AIJ_DISABLED, after-image journaling is being disabled
temporarily for the Convert operation
%RMU-I-LOGCONVRT, database root converted to current structure level
%RMU-S-CVTDBSUC, database DISK1:[TESTS]MF_PERSONNEL.RDB;1 successfully
converted from version V7.0 to V7.2
%RMU-I-LOGCREAIJ, created after-image journal file
DISK1:[TESTS]BACKUP_AFTER1.AIJ;2
%RMU-I-LOGMODSTR, activated after-image journal "AFTER1"
%RMU-W-DOFULLBCK, full database backup should be done to ensure future recovery
$RMU/CONVERT/ROLLBACK MF_PERSONNEL.RDB
%RMU-I-RMUTXT_000, Executing RMU for Oracle Rdb V7.2-00
Are you satisfied with your backup of
DISK1:[TESTS]MF_PERSONNEL.RDB;1 and your backup of
any associated .aij files [N]? Y
%RMU-I-AIJ_DISABLED, after-image journaling is being disabled
temporarily for the Convert operation
%RMU-I-LOGCONVRT, database root converted to current structure level
%RMU-I-CVTROLSUC, CONVERT rolled-back for DISK1:[TESTS]MF_PERSONNEL.RDB;1
to version V7.0
%RMU-I-CANTENAAIJ, The JOURNAL is now DISABLED. RMU CONVERT can not enable
the JOURNAL for previous versions. You must do this manually.
%RMU-W-DOFULLBCK, full database backup should be done to ensure future recovery
Example 2
This example is the same as Example 1, except fixed-size .aij
journals are being employed at the time of the conversion. The
first command in this example converts an Oracle Rdb release
7.1 database with fixed-size .aij files to an Oracle Rdb release
7.2 database. Because the Nocommit qualifier is specified in
the first command, you can roll back the converted database (the
Oracle Rdb release 7.2 database) to the original Oracle Rdb V7.1
database.
After-image journaling is disabled while the database is being
converted. After the database is converted, Oracle RMU activates
the next fixed-size .aij file and enables after-image journaling.
Note that .aij files are version specific. You should perform
a full backup operation after a conversion because the old .aij
files are incompatible with the newly converted database.
In the second command, the converted database is rolled back to
the original database.
$RMU/CONVERT/CONFIRM/NOCOMMIT MF_PERSONNEL.RDB
%RMU-I-RMUTXT_000, Executing RMU for Oracle Rdb V7.2-00
Are you satisfied with your backup of DISK1:[TESTS]MF_PERSONNEL.RDB;1
and your backup of any associated .aij files [N]? Y
%RMU-I-AIJ_DISABLED, after-image journaling is being disabled
temporarily for the Convert operation
%RMU-I-LOGCONVRT, database root converted to current structure level
%RMU-S-CVTDBSUC, database DISK1:[TESTS]MF_PERSONNEL.RDB;1 successfully
converted from version V7.1 to V7.2
%RMU-I-LOGMODSTR, activated after-image journal "AFTER2"
%RMU-W-DOFULLBCK, full database backup should be done to ensure future recovery
$RMU/CONVERT/ROLLBACK MF_PERSONNEL.RDB
%RMU-I-RMUTXT_000, Executing RMU for Oracle Rdb V7.2-00
Are you satisfied with your backup of
DISK1:[TESTS]MF_PERSONNEL.RDB;1 and your backup of
any associated .aij files [N]? Y
%RMU-I-AIJ_DISABLED, after-image journaling is being disabled
temporarily for the Convert operation
%RMU-I-LOGCONVRT, database root converted to current structure level
%RMU-I-CVTROLSUC, CONVERT rolled-back for
DISK1:[TESTS]MF_PERSONNEL.RDB;1 to version V7.1
%RMU-I-CANTENAAIJ, The JOURNAL is now DISABLED. RMU CONVERT can not
enable the JOURNAL for previous versions. You must do this manually.
%RMU-W-DOFULLBCK, full database backup should be done to ensure future recovery
Example 3
The following command converts all the databases in DISK1:[RICK]
and its subdirectories and also the SPECIAL_DB database that
is identified by its data dictionary path name. The Noconfirm
qualifier is specified, so Oracle RMU does not request user
input. The Nocommit qualifier is not specified, so the default
qualifier, Commit, is used by default and the converted databases
cannot be rolled back.
$ RMU/CONVERT/NOCONFIRM DISK1:[RICK...]*.RDB,CDD$TOP.RICK.SPECIAL_DB -
_$ /PATH
Example 4
The following command converts an Oracle Rdb release 7.0 database
to release 7.2. In addition, it reserves space in the database
root file of the converted database for four .aij files. After-
image journaling is not enabled at the time the Convert command
is issued.
$RMU/CONVERT/CONFIRM/RESERVE=(AIJ=4)/COMMIT MF_PERSONNEL
%RMU-I-RMUTXT_000, Executing RMU for Oracle Rdb V7.2-00
Are you satisfied with your backup of DISK1:[TESTS]MF_PERSONNEL.RDB;1
and your backup of any associated .aij files [N]? Y
%RMU-I-LOGCONVRT, database root converted to current structure level
%RMU-W-DOFULLBCK, full database backup should be done to ensure future recovery
%RMU-S-CVTDBSUC, database DISK1:[TESTS]MF_PERSONNEL.RDB;1 successfully
converted from version V7.0 to V7.2
Example 5
The following example shows how the contents of a batch file
might look if you were to issue the RMU Convert command with the
Confirm qualifier from a batch job.
$ RMU/CONVERT/COMMIT/CONFIRM USER1:[COLLECT.V71DB]MF_PERSONNEL
Y
Y