DB2 - Problem description
Problem IC66588 | Status: Closed |
ACTION SCRIPTS IS EXECUTED WHEN FIRST EVALUATIONS OF HEALTH INDICATORS IF ACTION CONDITION IS SET AS ALLALERTS. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problem description: | |
Action condition ALLALERTS has been added on alert configuration in DB2 V9.1. The condition handles any changes in the state, including when the state changes from warning to normal. However, running action scripts for 'unknown' to 'normal' state is not correct. The state changes will be occurred after the first evaluation of health indicators. The steps illustrates one of the scenario causing this problem: 1. Create a database and setup alert action with action condition 'allalerts'. db2 create db testdb db2 update alert cfg for tablespaces using ts.ts_op_status set actionsenabled yes db2 update alert cfg for tablespaces using ts.ts_op_status add action script myscript.sh type os on allalert 2. Activate the database. db2 activate db testdb | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users who use ALLALERTS on alert configration. * **************************************************************** * PROBLEM DESCRIPTION: * * Action condition ALLALERTS has been added on alert * * configuration in DB2 V9.1. The condition handles any changes * * in the state, including when the state changes from warning * * to normal. * * However, running action scripts for 'unknown' to 'normal' * * state is not correct. The state changes will be occurred * * after the first evaluation of health indicators. * **************************************************************** * RECOMMENDATION: * * Please upgrade to DB2 V9.8 fixpack 3 or later. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.8 Fix Pack 3. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.02.2010 21.12.2010 21.12.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.8.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.8.0.3 |