DB2 FOR LUW / DB2FORLUW / 980 - DB2

Beginning with DB2 version 9.5 Fixpak 3 and Version 9.7 GA, LOAD 
memory allocation behaviour changed.  While it is more 
efficient, in some cases a combination of fragmentation and 
large allocations can result in SQL0973N - failure to allocate 
memory from the Utility Heap. 
 
The expected db2diag.log entry is : 
2009-09-22-21.52.37.592451-240 I367406661E568    LEVEL: Error 
PID : 8318         TID  : 193441294688 PROC : db2sysc 2 
INSTANCE: db2inst1        NODE : 000   DB   : SAMPLE 
APPHDL : xxxxx         APPID: xxxxx 
AUTHID : db2inst1 
EDUID : 4582         EDUNAME: db2lload 0 
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 
DATA #1 : String, 145 bytes 
LOADID: 51624.2009-09-22-21.52.36.240048.10 (7;784) 
Failed to enable fast memblocks , -1961951227, (nil), Detected 
in file:sqlulbuf2.C, Line:1773 
 
If db2pd -db <db> -memsets can be issued after the failure, it 
may be observed that there is a sufficient amount of unused 
commited memory available in database memory : 
 
Memory Sets: 
Name      Size(Kb)  Unrsv(Kb)  Used(Kb)   HWM(Kb)   Cmt(Kb) 
Uncmt(Kb) 
SAMPLE    13851968   5897216  6837888    7721600    13562240 
70400 
 
In the above example, Commited memory is far above Used memory, 
and should be available for LOAD, which instead failed with 
SQL0973N.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Systems with a high frequency of LOAD operations             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.8 Fix Pack 4.                       * 
****************************************************************

A workaround exists.  Increasing the amount of commited memory 
that DB2 will cache will reduce fragmentation, allowing large 
allocations to succeed.  This can be accomplished by the command 
: 
" db2 update db cfg for <database> using DB_MEM_THRESH 100 " 
This is dynamic if issued while connected to the database.  Some 
increase in memory usage may be observed.

DB2 Version 9.8 Fix Pack 4 for AIX and Linux
 DB2 Version 9.8 Fix Pack 5 for AIX and Linux
 

Problem first fixed in DB2 Version 9.8 Fix Pack 4

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

06.05.2010
12.08.2011
12.08.2011

9.8.FP4