Skip to Content

Monitoring DB2 agent and subagent activity

Monitoring DB2 agents and subagents can provide critical information that you can use to tune your databases.

The ProblemDB2Agents parameter is active from startup. This parameter does not show values, however, until Alarm1 or Alarm2 is activated for any parameters in the DB2_AGENT, DB2EEE_AGENT and DB2EEE_SUBAGENT classes, which track agent and subagent activity.

The ProblemDB2Agents parameter is displayed below the Parameters icon at the DB2 instance level in the console and provides an annotated data point with a snapshot of the agent (application), SQL statement information (if available), and the parameter and value that caused the alarm.

Although the ProblemDB2Agents parameter is active from startup, you must activate the recovery action provided under each of the parameters that you want to monitor. The recovery actions for Alarm1 and Alarm2 produce annotated data points in the associated parameter and the ProblemDB2Agents parameter when they are triggered. By default, the CurrLockWaitTime parameter, which has a preset alarm threshold, uses this recovery action.

Refer to the parameter section in the online Help for a list of the parameters that you can configure for ProblemDB2Agents monitoring.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for DB2 Universal Database 9.0