Activities Overview

In the user menu Current Status (see OLTP or liveCache), there is, among other things, an overview of the database activities since the last start of the database monitoring or liveCache monitoring functions.

You can reset the monitoring data.



       1.      Open the Database Assistant (transaction DB50) or the liveCache Assistant (transaction LC10).

       2.      Choose Current Status ® Activity Overview.


The system displays the following information in the overview:

SQL Statements

In the SQL Statements area, you can find information about the SQL statements:

SQL Statements

Number of SQL statements sent to the database system to be executed. A direct indication of database activity.


Number of dynamic SQL statements.


Number of executed dynamic SQL statements.


Unsuccessful database operations, usually caused by terminated applications.


Successful database operations.

Updates, Selects and Fetches, Creates, Alters, Drops, Deletes, Inserts

Number of individual SQL statements, possibly with row information

The ratio between ROLLBACK actions and COMMIT actions can indicate logical inconsistencies in one or more SQL statements.

I/O Activity

In the I/O Activity area, you can see information about the I/O activities that were triggered by the database system. This includes information about the logical and physical read and write transactions.

In a physical read or write activity, the system accesses a volume directly. A logical read or write activity, on the other hand, uses data stored in the data cache or another cache.

See also:

I/O Operations (OLTP/ liveCache)

Lock Activity

The Lock Activity area gives you information about the maximum number of available database locks (entries) as well as the number of locks since the database start or liveCache monitoring. If the number of set locks is approaching the number of available locks, it is a good idea to raise the value of the general database parameter MAXLOCKS.

Escalations shows the total number of rows locked by a single user session. If more than a certain percentage of the rows of a table are locked by a single user session, then the database system locks the entire table. The threshold for Escalations follows the MAXLOCKS values for this database instance.

If a locked object is requested again, a lock conflict occurs. If a large number of collisions occurs in your system, this means that a specific lock is being held too long, or multiple users are trying to access the same part of the database too often.

The values of Lock Owner and Lock Requester refer to the locks at the time the transaction is executed.

See also:

SQL Locks (OLTP/ liveCache)

Logging Activity

The Logging Activity area shows you, among other things, the number of log pages (written log pages).

If the value of Log I/O Queue Overflow is greater than 0, increase the size of the log queue.

Scan and Sort Activity

The Scan and Sort Activity area shows you, among other things, information about table scans.

Keep the number of table scans to a minimum, since a high number of sequential scans can have a negative effect on database performance.

See also:

Database bottlenecks (OLTP/ liveCache)

Resetting Monitor Data

If you want to monitor the database status at the current time, choose Activity Monitor ® Reset Monitor Data. All relevant database system tables are initialized and the statistical data for database monitoring is collected from this time.