DB2 FOR LUW / DB2FORLUW / A10 - DB2

DB2 INSTANCE MAY TRAP WITH SIGNAL #11 ON SQLKQSND FUNCTION 
 
A select statement in a multi partitioned env. can crash the 
instance with Signal#11. 
 
The observed stack trace will be as follows: 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0900000001B4C13C 
sqlkqsnd__FP8SQLKQ_CBP8sqeAgentiPP10sqkfBufferT3Us + 0x294 
0x0900000001B4EDAC sqlktsnd__FP9sqlri_taoiUs + 0x210 
0x0900000001B51484 
sqlkt_pack_tuple__FP10SQLD_FIELDP9sqlri_taolPP10SQLD_VALUEP5sqlc 
aUsP8sqeAgent + 0x15B4 
0x090000000357B6A4 
sqlktins__FP7sqlr_dbP8sqeAgentP10sqlri_iudoP5sqlcaUs + 0x720 
0x09000000055F9DDC sqlritqb__FP8sqlrr_cb + 0x6A0 
0x0900000002B0FFC8 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 
0x30 
0x09000000048E1908 sqlrr_dss_router__FP8sqlrr_cb + 0xC30 
0x090000000319472C 
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x424 
0x09000000031958DC @82@sqleSubRequestRouter__FP8sqeAgentPUiPUl + 
0x3F4 
0x0900000003198218 sqleProcessSubRequest__FP8sqeAgent + 0x50C 
0x0900000002745BA0 RunEDU__8sqeAgentFv + 0x67C 
0x090000000274A1A0 EDUDriver__9sqzEDUObjFv + 0x13C 
0x090000000274A028 sqlzRunEDU__FPcUi + 0x10 
0x09000000027525A8 sqloEDUEntry + 0x264 
</StackTrace> 
 
The problem is a timing issue that can only happen if the access 
plan contains an MDTQ, and if the execution of the query plan 
features an "early out" scenario.  The most common form of 
"early out" is a fetch first n clause that will exit out of the 
query once the required number of rows are met.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW V10.1 FixPack4                            * 
****************************************************************

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First Fixed in DB2 LUW V10.1 FixPack4

keiner bekannt / siehe Local-Fix

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

21.08.2013
30.07.2014
30.07.2014