Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC88305 Status: Closed

INSTANCE HANG POSSIBLE AFTER APPLICATION HEAP MEMORY ERROR IN FUNCTION
SQLRWFILTEREDAPPLICATIONITERATOR::EXECUTE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade the database server to V10 Fix Pack 2 or higher      * 
****************************************************************
Local Fix:
Increase the applheapsz  parameter or set it to AUTOMATIC to 
avoid the problem.
available fix packs:
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

Solution
This problem has first been fixed in V10 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.11.2012
11.02.2013
11.02.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList