1  –  transactions_field

    This field gives the number of completed database transactions.
    This is the count of the COMMIT and ROLLBACK statements that have
    executed.

2  –  __committed_field

    This field identifies the actual number of transactions that
    committed successfully to the database.

3  –  __rolled_back_field

    This field identifies the actual number of transactions that were
    aborted and were not applied to the database.

4  –  ____duration_x100_field_

    This field identifies the duration of the transaction rollback
    operation, expressed in hundredths of a second displayed as a
    whole number. For example, the value 500 is actually 5 seconds.

5  –  __prepared_field

    This field identifies the number of distributed transactions
    that have successfully "prepared" themselves for subsequent
    transaction commit.

6  –  __not_modified_field

    This field identifies the number of committed transactions that
    did not modify any database objects. This field includes both
    read-only and read/write transactions.

7  –  verb_successes_field

    This field gives the number of completed verbs that returned a
    successful status code.

8  –  verb_failures_field

    This field gives the number of completed verbs that returned
    an error status code. Errors include end-of-collection and
    deadlocks, as well as all other exception conditions.

9  –  __duration_x100_field

    This field identifies the duration of the verb failure rollback
    operation, expressed in hundredths of a second displayed as a
    whole number. For example, the value 500 is actually 5 seconds.

10  –  checkpoints_field

    This field identifies the number of checkpoints performed by
    users. This field does not include the initial checkpoint when
    the user first attaches to the database.

11  –  ___duration_x100_field

    This field displays the checkpoint duration, expressed in
    hundredths of a second displayed as a whole number. For example,
    the value 500 is actually 5 seconds.

12  –  RUJ file reads field

    This field displays the total number of read I/O operations
    performed on the RUJ journal during the transaction undo phase.
    The RUJ file is never written by the database recovery (DBR)
    process.

    This field includes both synchronous and asynchronous I/O read
    requests.

13  –  ____file_writes_field_

    This field displays the total number of write I/O operations
    performed on the RUJ journal during the transaction phase.

    This field includes both synchronous and asynchronous I/O read
    requests.

14  –  ____file_extend_field_

    This field identifies the number of times an RUJ file has been
    extended.