Buffer pool data logical reads             = Not Collected

Buffer pool data physical reads            = Not Collected

Asynchronous pool data page reads          = Not Collected

[...]

The snapshot collects database level information for database 

DB2_EMP

. Some of 

the returned parameters display point in time values such as the number of 

currently connected applications:

Applications connected currently           = 1

Some parameters represent cumulative values like the number of connect 

statements issued against the database:

Application connects                       = 7

Some parameters can contain historical values like the maximum number of 

concurrent connections that have been observed on the database:

High water mark for connections            = 3

The cumulative or historical values relate to the point in time, since the last 

counters' initialization. The counters can be reset to zero by the 

RESET MONITOR

command, or by the appropriate DB2 event. With the mentioned Example 9 9, 

database deactivation and activation will reset all the database level counters. 

Example 9 10 shows how to reset monitors for an entire instance and for the 

specific database.

Example 9 10   Resetting snapshot monitor counters

db2 reset monitor all

db2 reset monitor for database db2_emp

To optimize database performance in a default DB2 configuration, most of the 

snapshot monitor elements are not collected. Because of that reason, in 

Example 9 9 the value 

Not Collected

 was displayed for the buffer pool statistics. 

DB2 UDB contains monitor switches to provide database administrators with the 

option of constraining the collection of monitor elements. Current monitor 

switches set for the session can be displayed from the command line with the 

GET 

MONITOR SWITCHES

 command as shown in Example 9 11.

Example 9 11   Displaying monitor switches

db2 get monitor switches

            Monitor Recording Switches

Switch list for db partition number 0

286 

MySQL to DB2 UDB Conversion Guide