Fixes are available
DB2 Version 9.5 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
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
APAR status
Closed as program error.
Error description
The health indicator calculates the alarm threshold using db2.mon_heap_max_size, but this max size may not be increased even though the MON_HEAP_SZ is configured as AUTOMATIC. As a result, the following message is continuously logged in db2diag.log. FUNCTION: DB2 UDB, Health Monitor, HealthIndicator::update, probe:500 MESSAGE : ADM10500E Health indicator "Monitor Heap Utilization" ("db2.mon_heap_util") breached the "upper" alarm threshold of "95 %" with value "100 %" on "instance" "DB2". Calculation: "((db2.mon_heap_cur_size/db2.mon_heap_max_size)*100);" = "((327680 / 327680) * 100)" = "100 %". History (Timestamp, Value, Formula): "()"
Local fix
Workaround this issue by updating the alert configuration element THRESHOLDSCHECKED of the health indicator to the value of 'no'. Run the following command from the CLP when logged in as the instance owner: db2 update alert cfg for dbm using db2.mon_heap_util set THRESHOLDSCHECKED no
Problem summary
PROBLEM SUMMARY AUTOMATIC SETTING FOR MON_HEAP_SZ WILL NOT INCREASE DB2.MON_HEAP_MAX_SIZE PROBLEM DESCRIPTION The health indicator calculates the alarm threshold using db2.mon_heap_max_size, but this max size may not be increased even though the MON_HEAP_SZ is configured as AUTOMATIC. As a result, the following message is continuously logged in db2diag.log. FUNCTION: DB2 UDB, Health Monitor, HealthIndicator::update, probe:500 MESSAGE : ADM10500E Health indicator "Monitor Heap Utilization" ("db2.mon_heap_util") breached the "upper" alarm threshold of "95 %" with value "100 %" on "instance" "DB2". Calculation: "((db2.mon_heap_cur_size/db2.mon_heap_max_size)*100);" = "((327680 / 327680) * 100)" = "100 %". History (Timestamp, Value, Formula): "()" LOCAL FIX: Workaround this issue by updating the alert configuration element THRESHOLDSCHECKED of the health indicator to the value of 'no'. Run the following command from the CLP when logged in as the instance owner: db2 update alert cfg for dbm using db2.mon_heap_util set THRESHOLDSCHECKED no USER AFFECTED ALL
Problem conclusion
First fixed in DB2 UDB Version 9.5, FixPak 4
Temporary fix
Comments
APAR Information
APAR number
JR31509
Reported component name
DB2 UDB EXE WIN
Reported component ID
5724E4901
Reported release
950
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-12-18
Closed date
2009-05-29
Last modified date
2009-05-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 UDB EXE WIN
Fixed component ID
5724E4901
Applicable component levels
R950 PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 October 2021