Include=Action=include-type

    Specifies if deleted or modified records or transaction commit
    information is to be extracted from the after-image journal. The
    following keywords can be specified:

    o  Commit
       NoCommit

       If you specify Commit, a transaction commit record is
       written to each output stream as the final record for each
       transaction. The commit information record is written to
       output streams after all other records for the transaction
       have been written. The default is NoCommit.

       Because output streams are created with a default file name
       of the table being extracted, it is important to specify a
       unique file name on each occurrence of the output stream.
       The definition of "unique" is such that when you write to a
       non-file-oriented output device (such as a pipe or mailbox),
       you must be certain to specify a specific file name on each
       output destination. This means that rather than specifying
       Output=MBA1234: for each output stream, you should use
       Output=MBA1234:MBX, or any file name that is the same on all
       occurrences of MBA1234:.

       Failure to use a specific file name can result in additional,
       and unexpected, commit records being returned. However, this
       is generally a restriction only when using a stream-oriented
       output device (as opposed to a disk file).

       The binary record format is based on the standard LogMiner
       output format. However, some fields are not used in the commit
       action record. The binary format and contents of this record
       are shown in Commit Record Contents. This record type is
       written for all output data formats.

    Table 20 Commit Record Contents

                 Length (in
    Field        bytes)       Contents

    ACTION       1            "C"
    RELATION     31           Zero
    RECORD_TYPE  4            Zero
    DATA_LEN     2            Length of RM_TID_LEN, AERCP_LEN, RM_
                              TID, AERCP
    NBV_LEN      2            Zero
    TID          4            Transaction (Attach) ID
    PID          4            Process ID
    START_TAD    8            Transaction Start Time/Date
    COMMIT_TAD   8            Transaction Commit Time/Date
    TSN          8            Transaction ID
    RM_TID_LEN   4            Length of the Global TID
    AERCP_LEN    4            Length of the AERCP information
    RM_TID       RM_TID_LEN   Global TID
    AERCP        AERCP_LEN    Restart Control Information
    RDB$LM_      12           USERNAME
    USERNAME

       When the original transaction took part in a distributed,
       two-phase transaction, the RM_TID component is the Global
       transaction manager (XA or DDTM) unique transaction ID.
       Otherwise, this field contains binary zeroes.

       The AIJ Extract Recovery Control Point (AERCP) information is
       used to uniquely identify this transaction within the scope
       of the database and after-image journal files. It contains
       the .aij sequence number, VBN and TSN of the last "Micro Quiet
       Point", and is used by the Continuous LogMiner process to
       restart a particular point in the journal sequence.

    o  Delete
       NoDelete

       If you specify Delete, pre-deletion record contents are
       extracted from the aij file. If you specify NoDelete, no
       pre-deletion record contents are extracted. The default is
       Delete.

    o  Modify
       NoModify

       If you specify Modify, modified or added record contents are
       extracted from the .aij file. If you specify NoModify, then no
       modified or added record contents are extracted. The default
       is Modify.