I am running DB2 V9.5.5 64bit LUW on Windows. When DB2 is started, the health monitor fails to initialize and crashes. Any guidance for diagnosing this issue would be appreciated.
the system info is
Instance "TCMI01" uses "64" bits and DB2 code release "SQL09055"
with level identifier "06060107".
Informational tokens are "DB2 v9.5.500.784", "s091123", "WR21458", Fix Pack "5".
DATA #2 : System Info, 1568 bytes
System: WIN32_NT ON-DB2NODE001 6.1 AMD64 Family 6, model 44, stepping 2
CPU: total:24 online:24 Cores per socket:16 Threading degree per core:1
Physical Memory(MB): total:98294 free:83645 available:83645
Virtual Memory(MB): total:196586 free:159589
Swap Memory(MB): total:98292 free:75944

DB2Diag snippet


2011-05-12-11.18.36.026000-300 E131135F329 LEVEL: Event
PID : 9876 TID : 10608 PROC : db2syscs.exe
INSTANCE: TCMI01 NODE : 000
EDUID : 10608
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
MESSAGE : ADM7513W Database manager has started.
START : DB2 DBM

2011-05-12-11.18.36.073000-300 I131466F563 LEVEL: Severe (OS)
PID : 5208 TID : 3916 PROC : db2fmp64.exe
INSTANCE: TCMI01 NODE : 000
EDUID : 3916
FUNCTION: DB2 UDB, SQO Memory Management, sqlocshr, probe:140
MESSAGE : ZRC=0x850F0005=-2062614523=SQLO_NOSEG
"No Storage Available for allocation"
DIA8305C Memory allocation failure occurred.
CALLED : OS, -, OpenFileMapping
OSERR : 2 "The system cannot find the file specified."
DATA #1 : String, 24 bytes
Global\DB2SHMTCMI01_0DBM

2011-05-12-11.18.36.073000-300 I132031F429 LEVEL: Severe
PID : 5208 TID : 3916 PROC : db2fmp64.exe
INSTANCE: TCMI01 NODE : 000
EDUID : 3916
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpThreadInit, probe:20
MESSAGE : Failure during health monitor thread initialization
DATA #1 : Hexdump, 4 bytes
0x000000000012F678 : 0500 0F85 ....

2011-05-12-11.18.46.072000-300 E132462F477 LEVEL: Warning
PID : 9876 TID : 7300 PROC : db2syscs.exe
INSTANCE: TCMI01 NODE : 000
EDUID : 7300 EDUNAME: db2sysc
FUNCTION: DB2 UDB, routine_infrastructure, sqlerReturnFmpToPool, probe:999
DATA #1 : String, 34 bytes
Removing FMP from pool FMP handle:
DATA #2 : sqlerFmpHandle, PD_SQLER_TYPE_FMP_HANDLE, 16 bytes
fmpPid: 5208 pFmpEntry: 0x000007fffdedbeb0

2011-05-12-11.18.46.088000-300 E132941F2355 LEVEL: Warning
PID : 9876 TID : 7300 PROC : db2syscs.exe
INSTANCE: TCMI01 NODE : 000
EDUID : 7300 EDUNAME: db2sysc
FUNCTION: DB2 UDB, routine_infrastructure, sqlerReturnFmpToPool, probe:1000
DATA #1 : String, 10 bytes
Fmp Entry:
DATA #2 : sqlerFmpThreadList, PD_SQLER_TYPE_FMP_THREAD_LIST, 416 bytes
fmpTid: 0
next Ptr: 0x0000000000000000 prev Ptr: 0x0000000000000000
agentCB Ptr: 0x0000000000000000 fmpRow Ptr: 0x000007fffdedbea0
ipcResources Ptr: 0x000007fffdedbda0
useCount: 0 nestLevel: 0
refreshThreadClass: 0 assocBroken: 0
threadFlags: 0x00000000 fmpComHandle: 0x0000000000000000
sendBuffer: 0x0000000000000000 recvBuffer: 0x0000000000000000
bufferSize: 0
bytesSent: 0 bytesReceived: 0
sendLength: 0 bufferPosition: 0
fmpConditions:
0x000007FFFDEDBEB0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBEC0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBED0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBEE0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBEF0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF00 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF10 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF20 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF30 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF40 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF50 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF60 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF70 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF80 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF90 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBFA0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBFB0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBFC0 : 0000 0000 0000 0000 0000 0000 ............

2011-05-12-11.18.46.088000-300 E135298F3070 LEVEL: Warning
PID : 9876 TID : 7300 PROC : db2syscs.exe
INSTANCE: TCMI01 NODE : 000
EDUID : 7300 EDUNAME: db2sysc
FUNCTION: DB2 UDB, routine_infrastructure, sqlerReturnFmpToPool, probe:1001
DATA #1 : String, 8 bytes
Fmp Row:
DATA #2 : sqlerFmpRow, PD_SQLER_TYPE_FMP_ROW, 496 bytes
fmpPid: 5208
fmpPoolList Ptr: 0x0000000000000000 fmpForcedList Ptr: 0x0000000000000000
nextFmpCB Ptr: 0x0000000000000000 prevFmpCB Ptr: 0x0000000000000000
fmpIPCList Ptr: 0x000007fffdedc0c0
stateFlags: 0x00000028 numFmp32Attaches: 0
numActiveThreads: 0 numPoolThreads: 0
fmpCodePage: 0 fmpRowUseCount: 0
active: 0x01 rowLoaderValidate: 0x00
ipcLatch:
0x000007FFFDEDBEA4 : 0000 A501 ....
rowLatch:
0x000007FFFDEDBEA8 : 0000 A601 ....
fmpAgentList:
0x000007FFFDEDBEB0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBEC0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBED0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBEE0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBEF0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF00 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF10 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF20 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF30 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF40 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF50 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF60 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF70 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF80 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBF90 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBFA0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBFB0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBFC0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBFD0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBFE0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDBFF0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDC000 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDC010 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDC020 : A0BE EDFD FF07 0000 A0BD EDFD FF07 0000 ................
0x000007FFFDEDC030 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FFFDEDC040 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2011-05-12-11.18.46.088000-300 I138370F350 LEVEL: Warning
PID : 9876 TID : 7300 PROC : db2syscs.exe
INSTANCE: TCMI01 NODE : 000
EDUID : 7300 EDUNAME: db2sysc
FUNCTION: DB2 UDB, routine_infrastructure, sqlerQueryHmonExistence, probe:99
MESSAGE : Health Monitor Process crashed.

Health Monitor has been depricated by IBM. Shut it off (dbm config parm).

It should still be active in V9.5 it is deprecated in 9.7 along with control center. .This is what I found on health monitor
"Health Monitor has been deprecated
The Health Monitor has been deprecated in DB2 Version 9.7 and might be discontinued in a future release. Start using Data Studio to monitor the health of your instances and databases. Visit the Data Studio product page at IBM - IBM Data Studio - Software for details about product offerings and downloads."
IBM DB2 9.7 for Linux, UNIX and Windows Information Center