DB2 FOR LUW / DB2FORLUW / 970 - DB2

You may encounter an instance trap after a LOAD operation fails 
(usually due to out of system resources) at a specific place 
very early on (at LOAD startup stage). 
 
The db2diag.log may show the following message indicating out of 
memory condition, or other message indicating out of system 
resources: 
 
2011-07-03-22.08.15.079591+120 I289048634E522     LEVEL: Error 
PID     : 29498                TID  : 47458223191968PROC : 
db2agent (SAMPLE) 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
APPHDL  : 0-362                APPID: 
*LOCAL.db2inst1.110703200802 
AUTHID  : DB2INST1 
FUNCTION: DB2 UDB, data protection services, sqlpwpen, probe:10 
RETCODE : ZRC=0x8B0F0002=-1961951230=SQLO_NOMEM_DBH 
          "No memory available in 'Database Heap'" 
          DIA8302C No memory available in the database heap. 
 
The stack of failing LOAD buffer manipulator (db2lbm) looks 
like: 
 
ossDumpStackTrace 
OSSTrapFile::dump 
sqlo_trce 
sqloEDUCodeTrapHandler 
__invoke_dynamic_linker__ 
sqluTermLoadEDU 
sqluInitLoadEDU 
sqlulbuf 
sqloCreateEDU 
sqloSpawnEDU 
sqlulInitOneEDU 
sqlulInitNBM 
sqlulCreateQAndEDU 
sqluvload 
call_sqluvload 
 
It may be another LOAD process than db2lbm that fails; the 
common signature is sqluInitLoadEDU() calls sqluTermLoadEDU() 
and we trap inside sqluTermLoadEDU(). 
 
DB2 fails (due to out of system resource) early in LOAD 
initialization code before setting up some internal pointers. 
During LOAD termination DB2 frees resources and dereferences the 
not initialzed pointer and traps.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 LOAD users on Version 9.7 Fixpack 4                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5.                       * 
****************************************************************

n/a (Proactively avoid hitting out of system resources, would 
avoid hitting this issue.  For example, DB2 system should be 
tuned during initial setup time (taking into consideration the 
expected workload) so that we will not run out of Database Heap 
memory.  Detailed DB2 setup/tuning instructions are beyond the 
scope of this APAR -- please refer to appropriate DB2 
documentation.)

DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in Version 9.7 Fix Pack 5.

keiner bekannt / siehe Local-Fix

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

21.07.2011
09.12.2011
09.12.2011

9.7.FP5