After_Journal[=file-spec]
    Noafter_Journal

                                   NOTE

       This qualifier is maintained for compatibility with versions
       of Oracle Rdb prior to Version 6.0. You might find it more
       useful to specify the Aij_Options qualifier, unless you are
       only interested in creating extensible after-image journal
       (.aij) files.

    Specifies how Oracle RMU is to handle after-image journaling and
    .aij file creation, using the following rules:

    o  If you specify the After_Journal qualifier and provide a file
       specification, Oracle RMU enables after-image journaling and
       creates a new extensible after-image journal (.aij) file for
       the database.

    o  If you specify the After_Journal qualifier but do not
       provide a file specification, Oracle RMU enables after-image
       journaling and creates a new extensible .aij file for the
       database with the same name as, but a different version number
       from, the .aij file for the database root file being moved.

    o  If you specify the Noafter_Journal qualifier, Oracle RMU
       disables after-image journaling and does not create a new
       .aij file.

    o  If you do not specify an After_Journal, Noafter_Journal,
       Aij_Options, or Noaij_Options qualifier, Oracle RMU retains
       the original journal setting (enabled or disabled) and the
       original .aij file state.

    You can only specify one, or none, of the following after-image
    journal qualifiers in a single RMU Move_Area command: After_
    Journal, Noafter_Journal, Aij_Options, or Noaij_Options.

    You cannot use the After_Journal qualifier to create fixed-size
    .aij files; use the Aij_Options qualifier.

    You can facilitate recovery by creating a new .aij file because a
    single .aij file cannot be applied across a move area operation
    that changes an area page size. A single .aij file cannot be
    applied across a move operation because the move operation is
    never recorded in the .aij file (and therefore the increase in
    page size is also not journaled). Therefore, when you attempt
    to recover the database, the original page size is used for
    recovery purposes. So, if the .aij file contains database insert
    transactions, these updates might have more free space associated
    with them than is available on the original page size. This
    results in an inability to recover the insert transaction, which
    in turn results in a bugcheck and a corrupted database.

    This qualifier is valid only when no users are attached to the
    database and only when the root file is moved.