Skip to Content

Acknowledging the ProblemDB2Agents alarm

Use this task to take the ProblemDB2Agents parameter out of an alarm state and to reset it to a normal state. The alarm alerts you that a parameter in the Agent or Subagent class has exceeded a threshold.

When ProblemDB2Agents parameter goes into an alarm state, click on the annotated data point in the ProblemDB2Agents parameter graph to get a report of the parameters and the application agents or subagents involved. This same annotation is available from a data point of the parameter triggering the alarm. Take the necessary actions to resolve the conflict and reset the alarm.

Warning

Note

The agent or subagent that triggered the alarm might have completed execution and thus the object and its parameters might no longer exist in the console.

Right-click on the Parameters icon below the DB2 instance icon and select Acknowledge ProblemDB2Agents Alarm. The ProblemDB2Agents parameter stops blinking.

Warning

Note

You can enable automatic alarm acknowledgement from the DB2_SETUP menu (or DB2EEE_SETUP for PATROL KM for DB2 UDB Enterprise-Extended Edition) by choosing Configuration > Configure KM Defaults > DB2 Global Settings, and then selecting Enable Automatic Alarm Acknowledgement for ProblemDB2Agents. You do not need to manually acknowledge each individual alarm; the CollAgent collector will reset the state of the parameter from alarm to OK.

Where to go from here

For more information about agents, see the following sections:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

 

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

BMC PATROL for DB2 Universal Database 9.0