Procedure documentationActivities Overview Locate this document in the navigation structure


The Performance user menu of the DBA Cockpit contains, among other things, an overview of the database activities since the last start of Database Monitoring. You can reset the monitoring data.


Open the DBA Cockpit (transaction DBACOCKPIT) and select   Performance   Activities Overview  .


The system displays the following information in the overview:

SQL Statements

In the SQL Statements area, you can find information about the executed 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 crashed applications


Successful database operations.

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

Number of individual SQL statements, possibly with row information

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.

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.

For more information, refer to: I/O Operations

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 set since the start of database monitoring. If the number of locks set approaches the number of available locks, it is a good idea to raise the value of the MAXLOCKS general database parameter.

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, the database system locks the entire table. The threshold for escalations follows the MAXLOCKS values for this database.

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 for lock owner and lock requester refer to the locks at the time the transaction is executed.

For more information, refer to: SQL Locks

Logging Activity

The Logging Activity area shows you, among other things, the number of log pages (written log pages, such as pages filled 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 size of log queues with the LOG_IO_QUEUE special database parameter and the number of the log queues with the LOG_QUEUE_COUNT support database parameter.

For more information, refer to: Concepts of the Database System, How Databases Log Data Changes

Scan and Sort Activity

The Scan and Sort Activity area shows you, among other things, information about table scans and data record sorting. Keep the number of table scans to a minimum, since a high number of sequential scans can have a negative effect on database performance.

For more information, refer to: Bottlenecks

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.

More Information

Database Activities

Concepts of the Database System, SQL, How Databases Store Data and Log Entries, Locks

Database Administration, General Database Parameters, Monitoring Databases