People I am getting the following error in the db2diag.log file
repeated over and over again with no apparent reason or souce.
2006-04-03-22.17.10.279000-240 I6310H330 LEVEL: Error (OS)
PID : 2372 TID : 2012
FUNCTION: DB2 Common, OSSe, OSSHIPCMemory::attach, probe:70
MESSAGE : ECF=0x9000000D Insufficent memory
CALLED : OS, -, MapViewOfFileEx OSERR:
ERROR_OUTOFMEMORY (8)
ARG #1 : Hex, 4 bytes
0x192C
We are on Win2k Server, db2 ESE 8.2.4, there is at least 700mb of free
REAL memory, the db2syscs.exe process is stable at 1.3gb with 2.5
installed.
Can anyone please advise where the fault may lay ?
Many thanks Tim
Liam Finnie - 04 Apr 2006 13:46 GMT
> People I am getting the following error in the db2diag.log file
> repeated over and over again with no apparent reason or souce.
[quoted text clipped - 15 lines]
>
> Many thanks Tim
Hi Tim,
This memory might be related to the health monitor, which asks for a
large contiguous block of memory. Processes on Windows are by default
limited to a 2GB virtual address space - from process explorer, you are
seeing that db2syscs.exe is using at least 1.3GB of memory, so at least
1.3GB of its virtual address space is consumed. However, this 1.3GB of
virtual address space consumption can be spread over db2syscs.exe's
entire 2GB virtual addres space range, not leaving enough contiguous
memory free for this memory request.
One thing you can consider looking into is the /3GB boot option on
Windows. This will give each process a 3GB virtual address space.
Otherwise, you can try reducing sizes of memory parameters, or you can
try contacting DB2 service for more assistance.
Cheers,
Liam.
p175 - 06 Apr 2006 23:03 GMT
Liam, that was it alright. I've stopped the healthmonitor and the issue
has since not repeated. It would of course be nice to know exactly how
much it was trying to ask for and whether this was configurable.
The /3GB boot option is unfortunately only available in Win2k Adv
Server and up, the basic server version does not support this
functionality.
Thanks for your help sir.