DB2 10.5 for Linux, UNIX, and Windows

dft_monswitches - Default database system monitor switches configuration parameter

This parameter allows you to set a number of switches which are each internally represented by a bit of the parameter.

Configuration type

Database manager

Applies to

Database server with local and remote clients
Database server with local clients
Partitioned database server with local and remote clients

Parameter type

Configurable Online

Propagation class

Immediate

Note: The change takes effect immediately if you explicitly ATTACH to the instance before modifying the dft_mon_xxxx switch settings. Otherwise the setting takes effect the next time the instance is restarted.

Default

All switches turned off, except dft_mon_timestamp, which is turned on by default

The parameter is unique in that you can update each of these switches independently by setting the following parameters:

dft_mon_uow: Default value of the snapshot monitor's unit of work (UOW) switch
dft_mon_stmt: Default value of the snapshot monitor's statement switch
dft_mon_table: Default value of the snapshot monitor's table switch
dft_mon_bufpool: Default value of the snapshot monitor's buffer pool switch
dft_mon_lock: Default value of the snapshot monitor's lock switch
dft_mon_sort: Default value of the snapshot monitor's sort switch
dft_mon_timestamp: Default value of the snapshot monitor's timestamp switch

Recommendation: Any switch (except dft_mon_timestamp) that is turned ON instructs the database manager to collect monitor data related to that switch. Collecting additional monitor data increases the processing time of the database manager which can impact system performance. Turning the dft_mon_timestamp switch OFF becomes important as CPU utilization approaches 100%. When this occurs, the CPU time required for issuing timestamps increases dramatically. Furthermore, if the timestamp switch is turned OFF, the overall cost of other data under monitor switch control is greatly reduced.

All monitoring applications inherit these default switch settings when the application issues its first monitoring request (for example, setting a switch, activating the event monitor, taking a snapshot). You should turn on a switch in the configuration file only if you want to collect data starting from the moment the database manager is started. (Otherwise, each monitoring application can set its own switches and the data it collects becomes relative to the time its switches are set.)