Hello guys,

Whats up? I am running a HADR DB2 Version 9.5 Fixpack 7

Today I checked the db2diag.log and i noticed a warning that is coming up each 2 hours and i actually dont know what do. Even after using google.

Does anyone have an idea how i can fix this? thanks in advance.

Disable Health Monitor on both primary and standby

update dbm cfg using health_mon off

Ok I am going to try that.
Thank you!

It also happens on a DB2 without HADR here.

My question is, could disabling Health Monitor cause some kind of lose of control, like running out of space, or even memory?

thanks

You will not hit on memory or disk space errors if you disable health monitor.

But, you have to monitor memory and disk using other tools if you need a warning



Cheers
Sathyaram

The DB2 Health Monitor has been depricated and will be removed in a future release. It almost always causes more problems then it solves.

Marcus and Sathyaram_s,

Good to know such pearls. Really make our path easier.

thanks a lot

Now there is this message. The Health Monitor was already OFF as shows cfg below. Does this message mean that the HMon is still running? Do I need to restart the server for this to take effect?


2012-02-16-03.01.31.474000-120 I1938267F1133 LEVEL: Warning
PID : 9956 TID : 10700 PROC : db2fmp64.exe
INSTANCE: DB2 NODE : 000
EDUID : 10700
FUNCTION: DB2 UDB, Health Monitor, HmonMainCB:repDBForFirstPlugin, probe:70
MESSAGE : Failed to verify and create policy for database "TOOLSDB ". rc =
90000505
DATA #1 : Hexdump, 136 bytes
0x000000000854E940 : 5351 4C43 4120 2020 8800 0000 DCFB FFFF SQLCA ........
0x000000000854E950 : 0700 4442 3248 4D4F 4E20 2020 2020 2020 ..DB2HMON
0x000000000854E960 : 2020 2020 2020 2020 2020 2020 2020 2020
0x000000000854E970 : 2020 2020 2020 2020 2020 2020 2020 2020
0x000000000854E980 : 2020 2020 2020 2020 2020 2020 2020 2020
0x000000000854E990 : 2020 2020 2020 2020 5351 4C45 4C4F 5354 SQLELOST
0x000000000854E9A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000000000854E9B0 : 0000 0000 0000 0000 2020 2020 2020 2020 ........
0x000000000854E9C0 : 2020 2030 3830 3034 08004

Default database monitor switches
Buffer pool (DFT_MON_BUFPOOL) = OFF
Lock (DFT_MON_LOCK) = OFF
Sort (DFT_MON_SORT) = OFF
Statement (DFT_MON_STMT) = OFF
Table (DFT_MON_TABLE) = OFF
Timestamp (DFT_MON_TIMESTAMP) = ON
Unit of work (DFT_MON_UOW) = OFF
Monitor health of instance and databases (HEALTH_MON) = OFF


thanks again

Yes, you need to restart the instance.

Thanks Marcus.

I discovered that there is also a 'show detail' option to the 'get dbm cfg' command, as there is for the 'get db cfg for...'

The prior step required is 'attach to <instance>' so it can work.

At the list I've got I could see that the HEALTH_MON parameter has two different values, the current 'ON' and the new one 'OFF' that will be applied after I restart the server.