DB2 FOR LUW / DB2FORLUW / A50 - DB2

When a query is run against a column organized table and the 
following conditions are met, we might hit a trap with a stack 
trace similar to the following. 
- group by (or select distinct) clause 
- an early termination scenario, such as fetch first n rows 
where the query will stop itself early 
- a timing scenario under certain memory conditions 
 
The stack trace will be similar to the following: 
</Siginfo_t> 
Signal #7 (SIGBUS): si_addr is 0x0000000000000000, si_code is 
0x00000080 (SI_KERNEL:Send by kernel.) 
</SignalDetails> 
... 
 
_ZN7ibm_cde5query19GroupByControlBlock31mergeSpilledEarlyMergedH 
TsToGHTEjRKiRKSt6vectorINS_5types8DataTypeENS_8services9Allocato 
rIS6_EEEPNS0_32LookupGroupingHashTableEvaluatorE + 0x0086 
 
_ZN7ibm_cde5query19GroupByControlBlock36completeGroupbyAggregati 
onProcessingEjPNS0_32LookupGroupingHashTableEvaluatorERNS0_16Run 
timeStatEntryE + 0x00e7 
 
_ZN7ibm_cde5query32LookupGroupingHashTableEvaluator26processInpu 
tsSynchronouslyEv + 0x006f 
 
_ZN7ibm_cde5query9Evaluator8evaluateEbbRNS1_21EvaluatorRestartSt 
ateEPNS0_19OptPredicateTrackerE + 0x07fd 
 
_ZN7ibm_cde5query17EvaluationRoutine8evaluateEjP15sql_static_dat 
a + 0x01aa 
 _ZN7ibm_cde5query9Scheduler13runThreadTaskEPvPi + 0x1255 
 _ZN7ibm_cde5query17cdeEntryPointImplEP8sqeAgentPvS3_ + 0x0070 
 _ZN12cdeInterface16startCdeSubagentEP8sqeAgent + 0x0087 
 _Z14sqlriInvokeCdeP8sqlrr_cb + 0x0041 
 _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x01cc 
 _Z16sqlrr_smp_routerP8sqlrr_cb + 0x0190 
 _Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0x0900 
 address: 0x00007FFFEF29D8E0 ; dladdress: 0x00007FFFEB4E7000 ; 
offset in lib: 0x0000000003DB68E0 ; 
 _Z21sqleProcessSubRequestP8sqeAgent + 0x02d7 
 _ZN8sqeAgent6RunEDUEv + 0x094b 
 _ZN9sqzEDUObj9EDUDriverEv + 0x00f4 
 sqloEDUEntry + 0x02f7 
 address: 0x00007FFFF7BC87B6 ; dladdress: 0x00007FFFF7BC1000 ; 
offset in lib: 0x00000000000077B6 ; 
 clone + 0x006d 
 .. 
 
This APAR will fix the above observed issue.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fixpack 5.                       * 
****************************************************************

First fixed in DB2 Version 10.5 Fixpack 5

keiner bekannt / siehe Local-Fix

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

18.08.2014
26.04.2015
26.04.2015