|
Problem IC69421
|
Status: Geschlossen |
HEALTH MONITOR PROVIDES ALERT WHEN MONITOR HEAP SET TO AUTOMATIC. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
Alert shows:
ADM10500E Health indicator "Monitor Heap Utilization"
("db2.mon_heap_util") breached the
"upper" alarm threshold of "XX %" with value "XXX %" on
"instance" "DB2". Calculation:
Health Monitor is sending Alert to db2 user while Monitor Heap
is set to Automatic. This APAR will fix the code in such a way
that
the health monitor code , by default will not monitor these
health indicators. For those users who don't have the
MON_HEAP_SZ
to 'AUTOMATIC' and they want these health indicator alarms, they
can enable using "update alert cfg " command. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* HEALTH MONITOR PROVIDES ALERT WHEN MONITOR HEAP SET *
* TOAUTOMATIC. *
****************************************************************
* RECOMMENDATION: *
* First Fixed in DB2 V9.5 Fixpak 7 *
**************************************************************** |
| Local-Fix: |
You can turn off the Monitor Alert switch by doing following:
db2 update alert cfg for database manager using
db2.mon_heap_util set THRESHOLDSCHECKED NO
db2 update alert cfg for databases using db.db_heap_util set
THRESHOLDSCHECKED NO |
| verfügbare FixPacks: |
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
|
| Lösung |
First Fixed in DB2 V9.5 Fixpak 7 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC69453 IC69456 IC71079
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 23.06.2010
20.01.2011
26.10.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.
|
| Problem behoben lt. FixList in der Version |
| 9.1.0.7
|
 |
| 9.5.0.7
|
|
