|
Problem IC73156
|
Status: Closed |
DB2SYSCS.EXE PROCESS VIRTUAL MEMORY EXHAUSTION ON 32-BIT WINDOWS DUE TO FRAGMENTATION |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
The DB2 server process, db2syscs.exe, on 32-bit Windows may
experience memory exhaustion due to excessive fragmentation in
DB2's private memory areas. The problem is caused by releasing
portions of virtual allocations to reduce real memory
consumption, this causes fragmentation between "free" managed
areas and "commited" managed areas.
Symptoms include:
- Windows memory analysis tools (such as vadump) reports growing
or large reserved memory areas.
- DB2's STMM (Self-Tuning Memory Manager) may gradually tune
down Database Memory as it is sensitive to available virtual
process memory space.
- db2diag.log may report virtual memory exhaustion. For
example:
FUNCTION: DB2 UDB, SQO Memory Management,
sqloLogMemoryCondition, probe:100
CALLED : OS, -, VirtualAlloc
OSERR : 8 "Not enough storage is available to process this
command."
MESSAGE : Private memory and/or virtual address space exhausted |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* 32-bit DB2 on Windows platform *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.5 Fix Pack 8 or higher *
**************************************************************** |
| Local Fix: |
A workaround is:
db2set DB2MEMDISCLAIM=NO
recycle the instance (db2stop, db2start)
This returns the behaviour to versions previous to 9.5. Memory
will be released only by freeing complete virtual allocations. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 Version 9.5 Fix Pack 8 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC73734 IC73735
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.12.2010
12.08.2011
12.08.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
