DB2 FOR LUW / DB2FORLUW / 970 - 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 DB2 server to V9.7 Fix Pack 7 or above           * 
****************************************************************

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

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
 

This problem has first been fixed in DB2 V9.7 Fix Pack 7

keiner bekannt / siehe Local-Fix

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

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

12.04.2012
30.10.2012
30.10.2012

9.7.FP7