## Displaying Database Activities

You can display the database activities in the Database Manager GUI.

### Prerequisite

The database instance is in the ONLINE operational state.

### Procedure

...

1. Select the required database instance in the list of database instances.
Connect to the DBM server for this database instance if necessary.

2. Choose Instance ® Information ® Activity.

3. You see a display of the database activities, split into the following sections:

¡ Commands: Information about the SQL statements

¡ I/O Activity: Information about the read and write activities

¡ Lock Activity: Information about lock activities

¡ Log Activity: Information about log activities

¡ Scan and Sort Activity: Information about table scans

#### Commands

The Commands section includes the following information about the SQL statements:

Statement Type | Explanation
SQL Commands | Number of SQL statements sent to the database system to be executed. A direct indication of database activity.
Prepares | Number of dynamic SQL statements.
Executes | Number of executed dynamic SQL statements.
Rollbacks | Unsuccessful database operations, usually caused by crashed applications
Commits | Successful database operations. The ratio between ROLLBACK actions and COMMIT actions can indicate logical inconsistencies in one or more SQL statements.
Updates, Selects and Fetches, Creates, Alters, Drops, DB procedure calls, Deletes, Inserts | Number of individual SQL statements, possibly with row information

#### I/O Activity

The I/O Activity section gives you information about I/O activities 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.

#### Lock Activity

The Lock Activity section gives you information about the maximum number of available database locks (Available Entries), as well as the number of locks that have been set. 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 you the total number of rows that have been locked in a single database session. As soon as the number of locked rows exceeds a specific percentage, 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 Requestor relate to the locks that exist when the transaction is executed.

#### Scan and Sort Activity

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

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