Example 1

    The following command reserves space for three .aij files, adds
    two .aij files to the mf_personnel database, and then enables
    after-image journaling:

    $ RMU/SET AFTER_JOURNAL/ENABLE/RESERVE=3           -
    _$ /ADD=(NAME=AIJ2, FILE=DISK1:[JOURNAL]AIJ_TWO)   -
    _$ /ADD=(NAME=AIJ3, FILE=DISK2:[JOURNAL]AIJ_THREE) -
    _$ MF_PERSONNEL
    %RMU-W-DOFULLBCK, full database backup should be done to
     ensure future recovery

    Example 2

    The following example demonstrates how to switch the current .aij
    file from DISK1:[DB]AIJ1 to the next available journal file in a
    fixed-size journal configuration, and then suppress the original
    journal in anticipation of maintenance on the disk that contains
    it. The last Oracle RMU command moves AIJ1 to a new disk and
    implicitly unsuppresses it.

    $ RMU/DUMP/HEADER=(JOURNAL) MF_PERSONNEL
       .
       .
       .
        AIJ Journaling...
         - After-image journaling is enabled
          - Database is configured for 5 journals
          - Reserved journal count is 5
          - Available journal count is 3
          - Journal switches to next available when full
          - 1 journal has been modified with transaction data
          - 2 journals can be created while database is active
          - Journal "AIJ1" is current
          - All journals are accessible
       .
       .
       .
    $ RMU/SET AFTER_JOURNAL/SWITCH_JOURNAL MF_PERSONNEL/LOG
    %RMU-I-OPERNOTIFY, system operator notification: Oracle Rdb Database
     USER1:[DB]MF_PERSONNEL.RDB;1 Event Notification
    After-image journal 0 switch-over in progress (to 1)

    %RMU-I-OPERNOTIFY, system operator notification: Oracle Rdb Database
     USER1:[DB]MF_PERSONNEL.RDB;1 Event Notification
    After-image journal switch-over complete

    %RMU-I-LOGMODSTR,     switching to after-image journal "AIJ2"
       .
       .
       .

    $ RMU/BACKUP/AFTER_JOURNAL MF_PERSONNEL DISK1:[DB]AIJ1_BCK/LOG
    %RMU-I-AIJBCKBEG, beginning after-image journal backup operation
    %RMU-I-OPERNOTIFY, system operator notification: Oracle Rdb Database
     USER1:[DB]MF_PERSONNEL.RDB;1 Event Notification
    AIJ backup operation started
    %RMU-I-AIJBCKSEQ, backing up after-image journal sequence number 2
    %RMU-I-LOGBCKAIJ, backing up after-image journal AIJ1 at 10:59:58.83
    %RMU-I-LOGCREBCK, created backup file DISK1:[DB]AIJ1_BCK.AIJ;1
    %RMU-I-OPERNOTIFY, system operator notification: Oracle Rdb Database
     USER1:[DB]MF_PERSONNEL.RDB;1 Event Notification
    AIJ backup operation completed

    %RMU-I-AIJBCKEND, after-image journal backup operation completed
     successfully
    %RMU-I-LOGAIJJRN, backed up 1 after-image journal at 11:00:02.59
    %RMU-I-LOGAIJBLK, backed up 254 after-image journal blocks
     at 11:00:02.59
    $ RMU/SET AFTER_JOURNAL/SUPPRESS=(NAME=AIJ1) MF_PERSONNEL/LOG
    %RMU-I-LOGMODSTR,     suppressed after-image journal "AIJ1"
    $ RMU/SET AFTER_JOURNAL MF_PERSONNEL -
    _$ /ALTER=(NAME=AIJ1,FILE=DISK2:[DB]AIJ1)/LOG
    %RMU-I-LOGMODSTR,     unsuppressed after-image journal "AIJ1"

    Example 3

    The following example turns on the automatic backup server for
    .aij files and defines a default backup file name:

    $ RMU/SET AFTER_JOURNAL /BACKUPS=(AUTOMATIC, -
    _$ BACKUP_FILE=DISK:[AIJ_BACKUPS]AIJ_BACKUP.AIJ) -
    _$ DB$DISK:[DIRECTORY]MF_PERSONNEL.RDB

    Example 4

    The following example turns off the automatic backup server for
    .aij files and removes the default backup file name:

    $ RMU/SET AFTER_JOURNAL /BACKUPS=(MANUAL,NOBACKUP_FILE) -
    _$ DB$DISK:[DIRECTORY]MF_PERSONNEL.RDB

    Example 5

    The following example changes the .aij backup file name without
    changing the setting of the AIJ backup server:

    $ RMU/SET AFTER_JOURNAL /BACKUPS= -
    _$ (BACKUP_FILE=NEW_DISK:[AIJ_BACKUPS]BETTER_BACKUP_NAME.AIJ) -
    _$ DB$DISK:[DIRECTORY]MF_PERSONNEL.RDB

    Example 6

    The following example sets a local and a global edit string for
    .aij backup files. When AIJ_ONE is backed up, it is appended with
    the string _LOCAL. When AIJ_TWO or AIJ_THREE are backed up, they
    are appended with the string _GLOBAL. Although it is unlikely
    that you would select these edit strings, they demonstrate the
    behavior of the Edit_Filename keyword when it is used with the
    Backup qualifier (global effect) versus the behavior of the Edit_
    Filename keyword when it is used with the Add qualifier (local
    effect).

    $ RMU/SET AFTER_JOURNAL/ENABLE/RESERVE=5 -
    _$ /BACKUP=EDIT_FILENAME=("_GLOBAL")/ADD=(NAME=AIJ1, -
    _$    FILE=DISK1:[AIJS]AIJ_ONE, -
    _$    BACKUP_FILE=AIJ1BCK, -
    _$    EDIT_FILENAME=("_LOCAL")) -
    _$  /ADD=(NAME=AIJ2, -
    _$    FILE=DISK1:[AIJS]AIJ_TWO,  -
    _$    BACKUP_FILE=AIJ2BCK) -
    _$  /ADD=(NAME=AIJ3, -
    _$    FILE=DISK1:[AIJS]AIJ_THREE, -
    _$    BACKUP_FILE=AIJ3BCK) -
    _$ MF_PERSONNEL

    $ !
    $ ! After these .aij files are backed up:
    $ !
    $ DIR .AIJ
    AIJ1BCK_LOCAL.AIJ;1
    AIJ2BCK_GLOBAL.AIJ;1
    AIJ3BCK_GLOBAL.AIJ;1
    AIJ_ONE.AIJ;1
    AIJ_THREE.AIJ;1
    AIJ_TWO.AIJ;1