DB2 FOR LUW / DB2FORLUW / 970 - DB2

Under low or no memory conditions on a busy system we can leave 
a partially initialized element in an internal structure causing 
a later call using that structure to trap. 
 
A likely stack is: 
 
<StackTrace> 
    -------Frame------ ------Function + Offset------ 
    0x090000004CEE372C 
sqlrr_sql_request_pre__FP14db2UCinterfaceUiiP16db2UCprepareInfoP 
15db2UCCursorInfo + 0x1EC 
    0x090000004DFAB8D4 
sqlrr_execute__FP14db2UCinterfaceP9UCstpInfo + 0x1414 
    0x090000004DA1E5F0 executeSection__10pvmPackageFP5sqlcaUib + 
0x8F0 
    0x090000004DA19F30 executeQuery__3PVMFUib + 0x1D0 
    0x090000004DA24B88 run__3PVMFv + 0xE88 
    0x0900000050521BA4 pvm_entry + 0x424 
    0x090000004C53B100 sqloInvokeFnArgs + 0x1A0 
    0x090000004F0E864C 
sqlriInvokerTrusted__FP10sqlri_ufobP21sqlriRoutineErrorIntfb + 
0x270C 
 
This is a boundary condition that can occur when a system is 
very low on memory and throwing a number of repeated memory 
errors, so there is a very narrow window in which this may 
occur.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Any users on a system where memory runs low                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade DB2 to at least V97 Fixpack 11                       * 
****************************************************************

n/a

Problem first fixed in V97 Fixpack 11

keiner bekannt / siehe Local-Fix

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

14.05.2015
03.11.2015
03.11.2015

9.7.FP11