InfoScale™ 9.0 Cluster Server Agent for DB2 Installation and Configuration Guide - Linux
- Introducing the Cluster Server Agent for DB2
- About agent functions for VCS Agent for DB2
- About IMF Integration functions for VCS Agent for DB2
- Installing and configuring DB2
- VCS requirements for installing DB2
- Setting up the DB2 configuration
- Installing and removing the Cluster Server Agent for DB2
- Configuring VCS service groups for DB2
- About DB2 configurations in VCS
- Before configuring the service group for DB2
- Configuring the VCS Agent for DB2 from Cluster Manager (Java Console)
- Configuring the VCS Agent for DB2 by editing the main.cf file
- Setting up in-depth monitoring of a DB2 instance
- Administering VCS service groups for DB2
- Appendix A. Troubleshooting Cluster Server Agent for DB2
- Appendix B. Resource type information for Cluster Server Agent for DB2
- Appendix C. Resource type attributes for DB2
- Appendix D. Sample configurations
Handling DB2 error codes during in-depth monitoring
The agent for DB2 comes with enhanced ability to handle DB2 errors during in-depth monitoring. The agent classifies DB2 errors according to their severity and associates predefined actions with each error code.
You can create a custom error handling file, db2error.dat. The file lists the DB2 errors and the associated actions that you want the agent to take when it encounters an error.
The file stores information in the following format:
SQL_error_string:action_to_be_taken
For example:
SQL1034N: IGNORE SQL1039N: WARN SQL1234N: FAILOVER
Table: Available actions for in-depth monitoring shows the available actions for in-depth monitoring.
Table: Available actions for in-depth monitoring
Action | Description |
---|---|
IGNORE | Ignores the error. |
UNKNOWN | Marks the resource state as UNKNOWN and sends a notification if the Notifier resource is configured. For more information about VCS notification, refer to the Cluster Server Administrator’s Guide. This action is typically associated with configuration errors. |
WARN | Marks the resource state as ONLINE and sends a notification if the Notifier resource is configured. This action is typically associated with low-severity errors. |
FAILOVER (Default) | Marks the resource state as OFFLINE. This faults the service group, which fails over to the next available system. This action is the agent's default behavior. If the DB2 error code that the agent encounters does not exist in the db2error.dat file, then the agent assumes this default behavior. |
NOFAILOVER | Freezes the service group temporarily and marks the resource state as OFFLINE. The agent also sends a notification if the Notifier resource is configured. This action is typically associated with the errors that are not system-specific. For example a failover to another node does not help a corrupt database, . |