home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IT00835 Status: Closed

IN LOW OR NO MEMORY CONDITIONS DB2 MAY TRAP IN SQLRR_SQL_REQUEST_PRE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Any using DB2                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix    * 
* Pack 4) for Linux, UNIX, and Windows                         * 
****************************************************************
Local Fix:
n/a
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix 
Pack 4) for Linux, UNIX, and Windows
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.04.2014
15.09.2014
15.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList