DB2 FOR LUW / DB2FORLUW / 950 - DB2

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

**************************************************************** 
* 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              * 
****************************************************************

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.

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
 

Problem first fixed in DB2 Version 9.5 Fix Pack 8

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC73734 IC73735 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

09.12.2010
12.08.2011
12.08.2011

9.5.FP8