The number of SQL statements is a direct indication of database activity.

The ratio of ROLLBACK actions to COMMIT actions may indicate logical inconsistencies in one or more SQL statements.

In a physical read or write activity, the system accesses a volume directly.

If the system accesses a volume logically, it uses information from the working memory.

If the number of locks set is ore or less the same as the number of locks available, increase the value for the general database parameter MaxSQLLocks.

Escalations show the total number of rows that are locked by a single user session.

If more than a certain percentage of the rows of a table is locked by a single user session, the database system locks the entire table. The database system calculates the threshold value for escalations from the value of the database parameter MaxSQLLocks.

If a locked object is requested again, a lock conflict occurs. If a large number of lock conflicts occurs in your system, this means that either a specific lock is being held too long or multiple users are frequently trying to access the same row. The values for lock owner and lock requester refer to the locks at the time the transaction is executed.

Log pages written with redo log entries

If the value of Log I/O Queue Overflow is greater than 0, increase the space available for log queues.

You can configure the number of log queues with the special database parameter LogQueues and the size of the log queues with a separate database parameter, LogQueueSize.