M

machine_identification - Host hardware identification monitor element

A string that describes the processor architecture. For example, x86 64 bit. The value returned for this identifier is determined by the operating system running on the host.

Table 1. Table Function Monitoring Information
Table Function	Monitor Element Collection Level
ENV_GET_SYSTEM_RESOURCES table function - Return system information	Always collected

max_agent_overflows - Maximum Agent Overflows monitor element

The number of times a request to create a new agent was received when the Maximum Number of Agents (maxagents) configuration parameter had already been reached.

Note: The max_agent_overflows monitor element is deprecated starting with DB2® Version 9.5. Using this monitor element will not generate an error. However, it does not return a valid value. This monitor element is no longer recommended and might be removed in a future release.

Table 2. Snapshot Monitoring Information
Snapshot Level	Logical Data Grouping	Monitor Switch
Database Manager	db2	Basic

Usage

If agent creation requests are still being received when the maxagents configuration parameter has been reached, this might indicate too high a workload for this node.

max_coord_stmt_exec_time - Maximum coordinator statement execution time monitor element

The maximum coordinator execution time of a single run of the statement, in milliseconds. This value will be zero at non-coordinator nodes or if the statement has not been executed.

Table 3. Table Function Monitoring Information
Table Function	Monitor Element Collection Level
MON_GET_PKG_CACHE_STMT table function - Get SQL statement activity metrics in the package cache	ACTIVITY METRICS BASE
MON_GET_PKG_CACHE_STMT_DETAILS table function - get detailed metrics for package cache entries (reported in DETAILS XML document)	ACTIVITY METRICS BASE

Table 4. Event Monitoring Information
Event Type	Logical Data Grouping	Monitor Switch
Package cache	pkgcache	ACTIVITY METRICS BASE

max_coord_stmt_exec_time_args - Maximum coordinator statement execution time arguments monitor element

An XML document that represents the input arguments provided to the statement that was running when the maximum execution time of a single run of the statement (max_coord_stmt_exec_time) took place on the coordinator member. This column is NULL if the statement has not yet run or if the statement has no input arguments. This document contains a parent element named max_coord_stmt_exec_time_args, which consists of one or more elements with the name max_coord_stmt_exec_time_arg. See Figure 1 for an example of the structure of the XML document.

Table 5. Table Function Monitoring Information
Table Function	Monitor Element Collection Level
MON_GET_PKG_CACHE_STMT table function - Get SQL statement activity metrics in the package cache	ACTIVITY METRICS BASE
MON_GET_PKG_CACHE_STMT_DETAILS table function - get detailed metrics for package cache entries (reported in DETAILS XML document)	ACTIVITY METRICS BASE

Table 6. Event Monitoring Information
Event Type	Logical Data Grouping	Monitor Switch
Package cache	pkgcache_stmt_args	ACTIVITY METRICS BASE

Usage

You can view the content of this document with the XMLPARSE scalar function. For example:

SELECT XMLPARSE(DOCUMENT MAX_COORD_STMT_EXEC_TIME_ARGS) 
  FROM TABLE(MON_GET_PKG_CACHE_STMT(NULL, NULL, NULL, -2));

Figure 1 shows an example of the contents of XML document returned by the preceding statement.

Figure 1. Sample content of max_coord_stmt_exec_time_args . In this example, the document shows that 15 arguments were passed to the statement.

<?xml version="1.0" encoding="ISO-8859-1" ?> 
 <max_coord_stmt_exec_time_args 
  xmlns="http://www.ibm.com/xmlns/prod/db2/mon" release="10010000">
   <max_coord_stmt_exec_time_arg>
      <stmt_value_index>1</stmt_value_index> 
      <stmt_value_isreopt id="0">no</stmt_value_isreopt> 
      <stmt_value_isnull id="0">no</stmt_value_isnull> 
      <stmt_value_type>INTEGER</stmt_value_type> 
      <stmt_value_data>5</stmt_value_data> 
   </max_coord_stmt_exec_time_arg>
   <max_coord_stmt_exec_time_arg>
      <stmt_value_index>2</stmt_value_index> 
      <stmt_value_isreopt id="0">no</stmt_value_isreopt> 
       <stmt_value_isnull id="0">no</stmt_value_isnull> 
       <stmt_value_type>VARCHAR</stmt_value_type> 
       <stmt_value_data>78</stmt_value_data> 
   </max_coord_stmt_exec_time_arg>
   <max_coord_stmt_exec_time_arg>
      <stmt_value_index>3</stmt_value_index> 
      <stmt_value_isreopt id="0">no</stmt_value_isreopt> 
       <stmt_value_isnull id="0">no</stmt_value_isnull> 
      <stmt_value_type>VARCHAR</stmt_value_type> 
      <stmt_value_data>john</stmt_value_data> 
   </max_coord_stmt_exec_time_arg>
   <max_coord_stmt_exec_time_arg>
      <stmt_value_index>4</stmt_value_index> 
      <stmt_value_isreopt id="0">no</stmt_value_isreopt> 
       <stmt_value_isnull id="0">no</stmt_value_isnull> 
      <stmt_value_type>VARCHAR</stmt_value_type> 
      <stmt_value_data>x</stmt_value_data> 
   </max_coord_stmt_exec_time_arg>
   <max_coord_stmt_exec_time_arg>
     <stmt_value_index>5</stmt_value_index> 
     <stmt_value_isreopt id="0">no</stmt_value_isreopt> 
     <stmt_value_isnull id="0">no</stmt_value_isnull> 
     <stmt_value_type>DATE</stmt_value_type> 
     <stmt_value_data>2001-02-12</stmt_value_data> 

                        ⋮

   <max_coord_stmt_exec_time_arg>
      <stmt_value_index>15</stmt_value_index>
      <stmt_value_isreopt id="0">no</stmt_value_isreopt> 
      <stmt_value_isnull id="0">no</stmt_value_isnull> 
      <stmt_value_type>DECIMAL</stmt_value_type> 
      <stmt_value_data>+0002000.55</stmt_value_data> 
    </max_coord_stmt_exec_time_arg>
  </max_coord_stmt_exec_time_args>

Entries for the following data types are recorded in this XML document, however, the actual values for arguments of these types are not captured in the STMT_VALUE_DATA element:

BLOB
CLOB
REF
BOOLEAN
Structured data types
DATALINK
LONG VARGRAPHIC
LONG VARCHAR
XML tyoes
DBCLOB
ARRAY types
ROW types
ROWID
CURSOR variables

Input arguments are recorded beginning with the one that appears first in the statement, and continuing with each one in succession. The number of input parameters that can be recorded is constrained only by the upper limit on the size of the BLOB containing the XML document. In practical terms, it is unlikely the number input arguments captured would ever cause this limit to be reached.

The schema for the XML document that contains this element can be found in the path sqllib/misc/DB2EvmonPkgCache.xsd.

max_coord_stmt_exec_timestamp - Maximum coordinator statement execution timestamp monitor element

The time the statement that produced the max_coord_stmt_exec_time value began execution.

Table 7. Table Function Monitoring Information
Table Function	Monitor Element Collection Level
MON_GET_PKG_CACHE_STMT table function - Get SQL statement activity metrics in the package cache	ACTIVITY METRICS BASE
MON_GET_PKG_CACHE_STMT_DETAILS table function - get detailed metrics for package cache entries (reported in DETAILS XML document)	ACTIVITY METRICS BASE

Table 8. Event Monitoring Information
Event Type	Logical Data Grouping	Monitor Switch
Package cache	pkgcache	ACTIVITY METRICS BASE

max_data_received_1024 - Number of Statements with Outbound Bytes Received Between 513 and 1024 Bytes monitor element

This element represents the number of statements or chains with outbound bytes received between 513 and 1024 inclusive.

Element identifier: max_data_received_1024
Element type: counter

Table 9. Snapshot Monitoring Information
Snapshot Level	Logical Data Grouping	Monitor Switch
DCS Database	dcs_dbase	Statement
DCS Application	dcs_appl	Statement
Data Transmission	stmt_transmissions	Statement