DB2 FOR LUW / DB2FORLUW / A10 - DB2

When running out of memory in the Database Heap, the instance 
may abend in SQLB_TPL::sqlbTPLIterator::getCurrentPage(). The 
symptoms written to the DB2 diagnostic log will show a memory 
allocation failure originating from sqlbTPL.C, for example: 
 
2012-10-26-17.01.06.055237-240 I2952365043A4032     LEVEL: 
Warning 
PID     : 9699348              TID : 54321          KTID : 
63176841 
PROC    : db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
SAMPLE 
APPHDL  : 0-12034              APPID: *N0.db2inst1.121026212255 
AUTHID  : DB2INST1             HOSTNAME: coralpib159 
EDUID   : 54321                EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, SQO Memory Management, sqlogmblkEx, 
probe:1000 
MESSAGE : ZRC=0x8B0F0002=-1961951230=SQLO_NOMEM_DBH 
          "No memory available in 'Database Heap'" 
          DIA8302C No memory available in the database heap. 
 
<...skipping...> 
 
DATA #8 : File name, PD_TYPE_OSS_MEM_FILE_NAME, 9 bytes 
sqlbTPL.C 
DATA #9 : Line of code, PD_TYPE_OSS_MEM_LINE_NUM, 8 bytes 
104 
 
<...skipping...> 
 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] pdLog 
  [1] sqlogmblkEx 
  [2] allocateNewPageListLink 
  [3] addOrUpdatePage 
  [4] sqlbAddPageToTPL 
  [5] sqlbufix 
  [6] sqlbUnFixPage 
  [7] sqldUpdateFSCR 
  [8] sqldAddRow 
  [9] sqldInsertRow 
  [10] sqldRowInsert 
  [11] sqlrinsr 
  [12] sqlrlCatalogScan::insert 
  [13] sqlr_update_catalogs 
  [14] sqlrLocalRunstats 
 
Shortly after, the instance will abend. An FODC_Trap package 
will be created, and the trap file will show getCurrentPage() on 
the top of the call stack. For example: 
 
SQLB_TPL::sqlbTPLIterator::getCurrentPage 
SQLB_TPL::sqlbTPLIterator::operator-> const 
SQLB_TPL::removeProcessedPages 
sqlbAddPageToTPL 
sqlbufix 
sqlbUnFixPage 
sqldUpdateFSCR 
sqldAddRow 
sqldInsertRow 
sqldRowInsert 
sqlrinsr 
sqlrlCatalogScan::insert 
sqlr_update_catalogs 
sqlrLocalRunstats

**************************************************************** 
* USERS AFFECTED:                                              * 
* See Error Description                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 for Linux, UNIX, and Windows Fix Pack 3  * 
****************************************************************

Tune your system to prevent memory allocation errors in the 
Database Heap, for example by increasing the DBHEAP database 
configuration parameter.

DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Problem first fixed in DB2 10.1 for Linux, UNIX, and Windows Fix 
Pack 3

not known / see Local fix

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

25.02.2013
27.09.2013
27.09.2013