The DB/2 Health Centre
Problem:
Working with a variety of customers on different platforms I see the following error occur in the Windows Event Log or db2diag.log on Linux.
ADM10500E Health indicator “Monitor Heap Utilization” (“db2.mon_heap_util”) breached the “upper” alarm threshold of “95 %” with value “180 %” on “instance” ”DB2″. Calculation: “((db2.mon_heap_cur_size/db2.mon_heap_max_size)*100);” = ”((589824 / 327680) * 100)” = “180 %”. History (Timestamp, Value, Formula):
Cause:
“The health monitor generated an alert because the alarm threshold for this health indicator was breached. This situation should be addressed immediately as it can lead to a degradation in database performance or an interruption in operation.”
Solution:
You can generally resolve this issue quickly by running the DB2 Control Centre Health Centre as shown below:
The warning is shown as an alarm:
Right click on the Alarm and select ‘Recommendation Advisor’:
A wizard is launched – and this is were you need some understanding of DB2 and of the current environment you are working in. Is this a once off alarm? Does this error display regularly in the event logs?
You have two options in the wizard to diagnose the problem further which is advisable or to immediately fix the pressing problem. The decision is yours. In my case the problem was occurring regularly so I need to extend the Heap Utilisation space – I selected the immediate resolution option, the wizard suggested as new upper limit value based on the previous alarms and I was good to go.
Please note the ‘immediate resolution’ option may not be the best option for your issue but it can be a quick way of resolving an issue and saves you having to dig out the old DB2 manual for the commands you require. (I know, I know – I hear those hardcore DBA’s saying I need to man-up – using the Control Centre is for girls 
Tags: database, DB/2, ECM, tip, troubleshooting
You can comment below, or link to this permanent URL from your own site.
