|
Problem IC64781
|
Status: Closed |
ACTION SCRIPTS IS EXECUTED WHEN FIRST EVALUATIONS OF HEALTH INDICATORS IF ACTION CONDITION IS SET AS ALLALERTS. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - 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 *
* alertconfiguration in DB2 V9.1. The condition handles any *
* changesin the state, including when the state changes from *
* warningto normal.However, running action scripts for *
* 'unknown' to 'normal'state is not correct. The state changes *
* will be occurredafter the first evaluation of health *
* indicators.The steps illustrates one of the scenario causing *
* thisproblem:1. Create a database and setup alert action with *
* actioncondition 'allalerts'.db2 create db testdbdb2 update *
* alert cfg for tablespaces using ts.ts_op_statusset *
* actionsenabled yesdb2 update alert cfg for tablespaces using *
* ts.ts_op_statusadd action script myscript.sh type os on *
* allalert2. Activate the database.db2 activate db testdb *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 V9.5 fixpack 6 or later. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.5 Fix Pack 6. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC65043 IC65044 IC66588
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.11.2009
09.09.2010
09.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
