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 IC93811 Status: Closed

IN ENVIRONMENTS WHERE SORT MEMORY IS CONSTRAINED SEGV CAN HAPPEN ON HASH
JOIN QUERIES DOING AGGREGATION

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
1.  Problem description 
 
DB2 can SEGV when a query does a hash join followed by 
aggregation. The typical stack will look like: 
 
?unknown + 0x0 
sqlriPeaItr__FP8sqlrr_cbP9sqlri_agoPl + 0xDDC 
sqlripea2__FP8sqlrr_cb + 0xCC 
sqldEvalDataPred__FP13SQLD_DFM_WORKPUlP10SQLD_DPRED + 0x304 
@113@sqldRIDlistFetch__FP8SQLD_CCBP12SQLD_ID_LIST + 0x118 
sqldRowFetch__FP8sqeAgentP8SQLD_CCBUlT3PP10SQLD_VALUEP8SQLZ_RIDT 
3P12SQLD_ID_LISTP9SQLP_LSN8 + 0x14C 
sqlriListFetch__FP8sqlrr_cb + 0x200 
sqlrihsjn__FP8sqlrr_cb + 0x3C 
sqlrievl__FP8sqlrr_cb + 0x20 
sqlriunn__FP8sqlrr_cbP10sqlri_stob + 0x21C 
sqlriset__FP8sqlrr_cb + 0x18 
sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x24 
sqlrr_process_fetch_request__FP14db2UCinterface + 0xF60 
sqlrr_fetch__FP14db2UCinterfaceP15db2UCCursorInfo + 0xE9C 
sqljs_ddm_cntqry__FP14db2UCinterfaceP13sqljDDMObject + 0x178C 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x1F8 
.sqljsParse.fdpr.clone.102__FP13sqljsDrdaAsCbP14db2UCinterfaceP8 
sqeAgentb + 0x13A4 
@73@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x280 
@73@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4 
@73@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x4E8 
sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0x21C 
RunEDU__8sqeAgentFv + 0x584 
EDUDriver__9sqzEDUObjFv + 0x13C 
sqlzRunEDU__FPcUi + 0x10 
sqloEDUEntry + 0x264 
 
There will two important messages in db2diag.log which will 
point to the issue. 
 
Message#1 
-------------- 
 
2013-06-19-04.50.47.802165-240 E14241455A535        LEVEL: 
Warning 
PID     : 44761092             TID : 33677          PROC : 
db2sysc 0 
INSTANCE: edad01               NODE : 000           DB   : 
TEDADB 
APPHDL  : 0-27015              APPID: 
30.135.65.102.52961.130617051714 
AUTHID  : WBIDBWEB             HOSTNAME: va10duvdb2006 
EDUID   : 33677                EDUNAME: db2agent (TEDADB) 0 
FUNCTION: DB2 UDB, runtime interpreter, sqlriPEXInitHashTable, 
probe:3229 
MESSAGE : Partial Early Aggregation/Distinct running with 
reduced memory 
 
Message#2 
---------------- 
2013-06-19-04.50.47.801532-240 I14240780A674        LEVEL: 
Warning 
PID     : 44761092             TID : 33677          PROC : 
db2sysc 0 
INSTANCE: edad01               NODE : 000           DB   : 
TEDADB 
APPHDL  : 0-27015              APPID: 
30.135.65.102.52961.130617051714 
AUTHID  : WBIDBWEB             HOSTNAME: va10duvdb2006 
EDUID   : 33677                EDUNAME: db2agent (TEDADB) 0 
FUNCTION: DB2 UDB, runtime interpreter, sqlriPEXInitHashTable, 
probe:3194 
DATA #1 : unsigned integer, 4 bytes 
2 
DATA #2 : unsigned integer, 4 bytes 
2 
DATA #3 : unsigned integer, 8 bytes 
4294975487  << This value indicates the defect has been hit ( 
Value is too large ) 
DATA #4 : unsigned integer, 8 bytes 
12497 
DATA #5 : unsigned integer, 8 bytes 
4181203339 << This value indicates the defect has been hit
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 FP3                                     * 
****************************************************************
Local Fix:
available fix packs:
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
Fixed in DB2 v10.1 FP3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.06.2013
25.09.2013
25.09.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList