Configuring and responding to alarms
A number of the PATROL for DB2 UDB parameters have preset alarm ranges. When the PATROL KM detects that the monitored object is in the alarm range, the KM responds according to the default parameter settings. You can configure the KM to react in a preventative way to certain alarms by adjusting the default settings. For parameter descriptions and default settings, see Application-classes.
The following table lists the parameters for which PATROL for DB2 UDB triggers alarms and lists the tasks or actions that you can perform with these alarms.
PATROL for DB2 UDB alarms
Parameter Alarm | Indication | Task or Action | Page |
|---|---|---|---|
ProblemDB2Agents | agent or subagent exceeded threshold limit | ||
DB2ServerOK | DB2 server terminated | ||
PctPagesUsed | tablespace capacity full | ||
CurrLockWaitTime | excessive database lock time | ||
Deadlocks | deadlock detected | ||
ChannelFailure | excessive number of channel failures | ||
|
|
|
|
DiagLogOK | keyword written to diagnostic log | ||
|
|