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  –  verb_successes_field

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

3  –  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.

4  –  synch_data_reads_field

    This field gives the number of read-I/Os (queued I/O requests)
    issued to the database storage area for single-file and multifile
    databases and snapshot files. This operation reads database pages
    synchronously from the database.

5  –  synch_data_writes_field

    This field gives the number of write-I/Os (queued I/O requests)
    issued to the database storage area for single-file and multifile
    databases and snapshot files. This operation writes modified
    database pages synchronously back to the database.

6  –  asynch_data_reads_field

    This field gives the number of read-I/Os (queued I/O requests)
    issued to the database storage area for single-file and multifile
    databases and snapshot files. This operation reads database pages
    asynchronously from the database.

7  –  asynch_data_writes_field

    This field gives the number of write-I/Os (queued I/O requests)
    issued to the database storage area for single-file and multifile
    databases and snapshot files. This operation writes modified
    database pages asynchronously back to the database.

8  –  RUJ file reads field

    This field gives the number of read-I/Os (queued I/O requests)
    issued to the database recovery-unit journal (.ruj) files. This
    operation reads before-image records from the .ruj file to roll
    back a verb or a transaction.

9  –  RUJ file writes field

    This field gives the number of write-I/Os (queued I/O requests)
    issued to the database recovery-unit journal (.ruj) files. This
    operation writes before-image records to the .ruj file in case
    a verb or transaction must be rolled back. Before-images must be
    written to the RUJ file before the corresponding database page
    can be written back to the database.

10  –  AIJ file reads field

    The number of read-I/Os issued to the database .aij file. If
    after-image journaling is not enabled for the database, this
    statistic will be zero.

11  –  AIJ file writes field

    This field gives the total number of write-I/Os (queued I/O
    requests) issued to the database after-image journal (.aij) file.
    If after-image journaling is not enabled for the database, this
    statistic will be zero. This operation writes after-image records
    to the .aij file to facilitate rollforward recovery using the RMU
    Recover command.

12  –  ACE file reads field

    This field gives the total number of read I/Os issued to the ACE
    file.

13  –  ACE file writes field

    This field gives the total number of write I/Os issued to the ACE
    file.

14  –  root_file_reads_field

    This field gives the number of read-I/Os (queued I/O requests)
    issued to the database root (.rdb) file. Oracle Rdb reads the
    .rdb file when a new user attaches to the database and when an
    .rdb file control block needs to be updated because of database
    activity on another VMScluster node.

15  –  root_file_writes_field

    This field gives the number of write-I/Os (queued I/O requests)
    issued to the database root (.rdb) file. Oracle Rdb writes to
    the .rdb file when a user issues a COMMIT or ROLLBACK statement.
    Other events also cause updates to the .rdb file.