You can display the database activities in the Database Manager GUI.
The database instance is in the ONLINE operational state.
Select the required database instance in the list of database instances. Choose Instance ® Information ® Activity.
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
The Commands section includes the following information about the SQL statements:
Command Type |
Command Function |
SQL Commands |
Number of SQL statements sent to the database system to be executed. A direct indicator 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. |
Updates, Selects and Fetches, Creates, Alters, Drops, DB procedure calls, Deletes, Inserts |
Number of SQL statements, possibly with row information |
The I/O Activity section gives you information about I/O activities triggered by the database system. This includes details of logical and physical read and write activities.
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.
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 locks that have been set approximates the number of available entries, you may need to increase 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 is based on the MAXLOCKS value for this database instance.
If a locked object is requested again, a lock conflict occurs. If a large number of lock conflicts occur 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.
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.