|
Problem IC65043
|
Status: Geschlossen |
ACTION SCRIPTS IS EXECUTED WHEN FIRST EVALUATIONS OF HEALTH INDICATORS IF ACTION CONDITION IS SET AS ALLALERTS. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* Users who use health alert with action condition ALLALERTS. *
****************************************************************
* 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 *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 V9.7 fixpack 2 or later. *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in Version 9.7 Fix Pack 2 (s100514). |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 09.12.2009
06.07.2010
06.07.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP2
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.2
|
 |
