The following tables describe the structures of the DB2 Problem Alert solution rules.
Table 90 Table Space ProblemRule Structure
Item |
Description |
---|---|
Title |
Table Space Problem |
Name |
DSNU086I |
Table |
DB2 |
Message |
DSNU086I csect ttttt I/O ERRORS ON SPACE=dddddddd. |
Message Description |
One or more I/O errors occurred while accessing a table space. |
Basic Scheduling Parameters |
Always schedule this rule. |
Runtime Scheduling Parameters |
No special considerations |
Global Variables |
None. |
Rule Logic |
This rule is triggered by the above DB2 message. The rule "shouts" a message identifying the problematic table space name to the database administrator. |
Rule Actions |
|
Activating the Rule |
Once scheduled, the rule is triggered whenever the above message is issued by the DB2 subsystem. |
Recommended Mode or Category |
During the testing period, activate the rule in LOG mode. Once you are satisfied with the results of the rule, change the mode to PROD to avoid log messages for the rule. The SolveWare category for this rule is 1—little or no customization is required before implementation. |
Table 91 Threads Are Unavailable Rule Structure
Item |
Description |
---|---|
Title |
Threads Are Unavailable |
Name |
DSNC011I |
Table |
DB2 |
Message |
DSNC011I xxxx TRANSACTION ABENDED BECAUSE THREADS ARE UNAVAILABLE |
Message Description |
The transaction identified by xxxx abended because a thread connection to DB2 was not available for the transaction. This indicates that the maximum number of thread connections had already been reached before the current transaction. |
Basic Scheduling Parameters |
Always schedule this rule. |
Runtime Scheduling Parameters |
No special considerations |
Global Variables |
None. |
Rule Logic |
This rule is triggered when the above DB2 message is issued. The rule "shouts" the DB2 message text to the database administrator. |
Rule Actions |
"Shouts" message text notifying U-SYSDBA of the thread-unavailability problem. |
Activating the Rule |
Once ordered, the rule remains active until message DSNC011I exceeds a predefined threshold. (For more information regarding threshold handling, see the following section.) |
Recommended Mode or Category |
During the testing period, activate the rule in LOG mode. Once you are satisfied with the results of the rule, change the mode to PROD to avoid log messages for the rule. The SolveWare category for this rule is 1—little or no customization is required before implementation. |
Parent Topic |