DB2 FOR LUW / DB2FORLUW / A10 - DB2

When an Application Heap memory error is observed in function 
SQLRWFILTEREDAPPLICATIONITERATOR::Execute 
the error handling code may leave a resource ( latch ) locked 
that may eventually lead to an instance hang. 
 
The db2diag.log will show the following sequence of messages : 
 
FUNCTION: DB2 UDB, WLM, sqlrwExpandableBuffer::getNextElement, 
probe:10 
CALLED  : DB2 UDB, WLM, sqlrwExpandableBuffer::getNextElement 
RETCODE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH 
          "No memory available in 'Application Heap'" 
          DIA8301C No memory available in the application heap. 
 
 
FUNCTION: DB2 UDB, WLM, sqlrwApplicationMetricsBuilder::execute, 
probe:10 
RETCODE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH 
          "No memory available in 'Application Heap'" 
          DIA8301C No memory available in the application heap. 
 
 
FUNCTION: DB2 UDB, WLM, 
sqlrwFilteredApplicationIterator::execut, probe:20 
CALLED  : DB2 UDB, WLM, sqlrwFilteredApplicationIterator::execut 
RETCODE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH 
          "No memory available in 'Application Heap'" 
          DIA8301C No memory available in the application heap. 
 
 
FUNCTION: DB2 UDB, WLM, sqlrwGetConnectionMetrics, probe:20 
RETCODE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH 
          "No memory available in 'Application Heap'" 
          DIA8301C No memory available in the application heap. 
 
 
Stack traces collected e.g. via db2fodc -hang will eventually 
lead to this latch : "SQLO_LT_sqeApplication__masterAppLatch" as 
the 
problematic latch.

**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade the database server to V10 Fix Pack 2 or higher      * 
****************************************************************

Increase the applheapsz  parameter or set it to AUTOMATIC to 
avoid the problem.

DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 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
 

This problem has first been fixed in V10 Fix Pack 2

keiner bekannt / siehe Local-Fix

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

17.11.2012
11.02.2013
11.02.2013