DB2 Version 9.7 for Linux, UNIX, and Windows

GET DATABASE MANAGER MONITOR SWITCHES command

Displays the status of the database system monitor switches.

Monitor switches instruct the database manager to collect database activity information. Each application using the database system monitor interface has its own set of monitor switches. A database manager-level switch is on when any of the monitoring applications has turned it on. This command is used to determine if the database system monitor is currently collecting data for any monitoring application.

Authorization

One of the following:
  • sysadm
  • sysctrl
  • sysmaint
  • sysmon

Required connection

Instance or database:
  • If there is neither an attachment to an instance, nor a connection to a database, a default instance attachment is created.
  • If there is both an attachment to an instance, and a database connection, the instance attachment is used.

To display the settings for a remote instance, or for a different local instance, it is necessary to first attach to that instance.

Command syntax

Read syntax diagramSkip visual syntax diagram
>>-GET--+-DATABASE MANAGER-+--MONITOR SWITCHES------------------>
        +-DB MANAGER-------+                     
        '-DBM--------------'                     

>--+----------------------------------------+------------------><
   +-AT DBPARTITIONNUM--db-partition-number-+   
   '-GLOBAL---------------------------------'   

Command parameters

AT DBPARTITIONNUM db-partition-number
Specifies the database partition for which the status of the database manager monitor switches is to be displayed.
GLOBAL
Returns an aggregate result for all database partitions in a partitioned database environment.

Examples

The following is sample output from GET DATABASE MANAGER MONITOR SWITCHES:

            DBM System Monitor Information Collected            

Switch list for db partition number 1                                                                
Buffer Pool Activity Information (BUFFERPOOL) = ON   06-11-2003 10:11:01.738377                                     
Lock Information                       (LOCK) = OFF             
Sorting Information                    (SORT) = ON   06-11-2003 10:11:01.738400                                     
SQL Statement Information         (STATEMENT) = OFF             
Table Activity Information            (TABLE) = OFF             
Take Timestamp Information        (TIMESTAMP) = ON   06-11-2003 10:11:01.738525
Unit of Work Information                (UOW) = ON   06-11-2003 10:11:01.738353        

Usage notes

The recording switches BUFFERPOOL, LOCK, SORT, STATEMENT, TABLE, and UOW are off by default, but can be switched on using the UPDATE MONITOR SWITCHES command. If any of these switches are on, this command also displays the time stamp for when the switch was turned on.

The recording switch TIMESTAMP is on by default, but can be switched off using UPDATE MONITOR SWITCHES. When this switch is on the system issues timestamp calls when collecting information for timestamp monitor elements. Examples of these elements are:
  • agent_sys_cpu_time
  • agent_usr_cpu_time
  • appl_con_time
  • con_elapsed_time
  • con_response_time
  • conn_complete_time
  • db_conn_time
  • elapsed_exec_time
  • gw_comm_error_time
  • gw_con_time
  • gw_exec_time
  • host_response_time
  • last_backup
  • last_reset
  • lock_wait_start_time
  • network_time_bottom
  • network_time_top
  • prev_uow_stop_time
  • rf_timestamp
  • ss_sys_cpu_time
  • ss_usr_cpu_time
  • status_change_time
  • stmt_elapsed_time
  • stmt_start
  • stmt_stop
  • stmt_sys_cpu_time
  • stmt_usr_cpu_time
  • uow_elapsed_time
  • uow_start_time
  • uow_stop_time

If the TIMESTAMP switch is off, timestamp operating system calls are not issued to determine these elements and these elements will contain zero. Turning this switch off becomes important as CPU utilization approaches 100%; when this occurs, the CPU time required for issuing timestamps increases dramatically.

Compatibilities

For compatibility with versions earlier than Version 8:
  • The keyword NODE can be substituted for DBPARTITIONNUM.