DB2 Health Monitor-Monitor Heap Utilization

12 January,2010 by

On a production system running DB29.5 on Red Hat Linux 4.6 .
If you want to keep the health monitor running, you can increase
the size of MON_HEAP_SZ to about 2048. But I decided to turn the Health
Monitors Off, due to overconsumption of memory.
These are OLTP databases. Since I’ve turned off the health monitor the system is running smoothly

Problem
——————————–
DM10500E Health indicator “Monitor Heap Utilization”
(“db2.mon_heap_util”) breached the “upper” alarm
threshold of”95 %”
with value “150%” on “instance” “db2instp”.
Calculation:
“((db2.mon_heap_cur_size/db2.mon_heap_max_size)*100);”
“((589824/
393216) * 100)”= “150 %”. History (Timestamp, Value,
Formula): ”
(16/11/200912:03:30.820296, 83, ((327680 / 393216) * 100))”

Resolution
——————————–

db2 update dbm cfg using HEALTH_MON OFF
db2stop and db2start to restart the instance.

Ref:Jack Vamvas

i am a sys admin which in herited a db2 server, and i get this same alert. how is disabling the monitor solving the problem? I guess a better question is, what does this alert mean and what do i need to correct, rather than just turn off the monitor?

Posted by: Cordy Dorian | Dec 12, 2011 6:08:32 AM

Hi Cordy Dorian, this was a problem I was experiencing up to DB2 9.5 . I turned them off , as it was crashing the DB2 server , and as there were severe resource constraints on the server – this was the pragmatic way to progress.
If you don’t want to turn them off – Steps to correct the problem include : a) increase mon_heap_sz – try initially doubling – if that isn’t enough double again.

DB2 Health Monitor-Monitor Heap Utilization

Share this:

Like this:

Leave a ReplyCancel reply

Discover more from ciquery