DB2 FOR LUW / DB2FORLUW / A10 - DB2

Upon hitting a failure, error handling in sqlra_get_var may trap 
if REOPT is enabled. 
 
Typically the trap will be preceded by a db2diag.log messages 
indicating the error, e.g: 
 
2015-01-05-21.54.48.004039+480 I53168609A586      LEVEL: Error 
PID     : 11796724             TID  : 605440      PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
APPHDL  : 0-56850              APPID: x.x.x.x.xxxxx.xxxxxxxxxxxx 
AUTHID  : DB2INST1 
EDUID   : 605440               EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, access plan manager, 
sqlra_sqlC_acquire_sibling, probe:10 
RETCODE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH 
          "No memory available in 'Application Heap'" 
          DIA8301C No memory available in the application heap. 
 
Followed by: 
 
2015-01-05-21.54.48.004883+480 I53169729A574      LEVEL: Error 
PID     : 11796724             TID  : 605440      PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
APPHDL  : 0-56850              APPID: x.x.x.x.xxxxx.xxxxxxxxxxxx 
AUTHID  : DB2INST1 
EDUID   : 605440               EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, access plan manager, sqlra_get_var, probe:350 
RETCODE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH 
          "No memory available in 'Application Heap'" 
          DIA8301C No memory available in the application heap. 
 
The stack in the trap file may look like: 
 
sqlra_get_var 
sqlrr_process_execute_request 
sqlrr_execute 
...

**************************************************************** 
* USERS AFFECTED:                                              * 
* Using DB2 for LUW with REOPT enabled.                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5                       * 
****************************************************************

N/A.

Problem first fixed in DB2 Version 10.1 Fix Pack 5

keiner bekannt / siehe Local-Fix

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

07.04.2015
21.07.2015
21.07.2015