DB2 FOR LUW / DB2FORLUW / A10 - DB2

1. ENVIRONMENT 
Server is running MPP/EEE (single node). 
DB21085I  This instance or install (instance name, where 
applicable: 
"inbcfmov") uses "64" bits and DB2 code release "SQL09077" with 
level 
identifier "08080107". 
Informational tokens are "DB2 v9.7.0.7", "s121002", "IP23367", 
and Fix Pack 
"7". 
Product is installed at "/opt/IBM/DB2/V9.7". 
 
2. PROBLEM DESCRIPTION 
An SQL which has following condition have "EDU has been 
suspended" message in v97fp7 only. 
 a) a 'col IN (...)' predicate 
 b) an additional local predicate <, <=, =, >=, > on the same 
column as the IN predicate 
 c) a total of more then 64 columns are used from all tables 
referenced in the sub-select containing the IN predicate. 
 
The following diagnostic tools will show problem is happening 
 
db2diag.log 
- You can check the message "EDU has been suspended" 
... 
EDUID   : 166801               EDUNAME: db2agent (BCFMOVDB) 0 
(suspended 
FUNCTION: DB2 UDB, RAS/PD component, pdSuspendEDU, probe:10 
MESSAGE : EDU has been suspended 
 
StackTrace 
- In the stack trace, sqlno_exists_in_set and 
sqlno_prop_compute_red_inlist_adjustments will be found 
-------Frame------ ------Function + Offset------ 
0x0900000006FF6D20 
sqlno_exists_in_set__FP13sqlno_globalsP9sqlno_sdbi9sqlno_set@glu 
e16E8 + 0x54 
0x09000000059520EC 
@155@sqlno_prop_compute_red_inlist_adjustments__FCP13sqlno_globa 
lsCP9sqlno_qtb + 0x224 
0x090000000400DC74 
sqlno_prop_compute_ff_adjustments__FP13sqlno_globalsP9sqlno_qtb 
+ 0x160 
0x090000000400EF84 
sqlno_plan_begin_opr__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_opr + 
0x1D0 
0x0900000004003D6C 
sqlno_each_opr__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_qunP9sqlnq_o 
pr + 0x2CC 
0x0900000004003944 
sqlno_walk_qun__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_oprP9sqlnq_q 
un + 0xFC 
0x0900000004003E6C 
sqlno_each_opr__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_qunP9sqlnq_o 
pr + 0x3CC 
0x0900000004003944 
sqlno_walk_qun__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_oprP9sqlnq_q 
un + 0xFC 
0x0900000004003E6C 
sqlno_each_opr__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_qunP9sqlnq_o 
pr + 0x3CC

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the latest level.                                 * 
****************************************************************

WORKAROUND 
 
DB2_CORRELATED_PREDICATES=NO_RED_IN 
 
The workaround disables the creation of cardinality adjustments 
that enable us to more accurately estimate the cardinality of 
subsequent joins after the application of the IN predicate. It 
is possible that inaccurate cardinality estimates may lead to 
poorly performing query access plans.

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
 

First fixed in V9.7

keiner bekannt / siehe Local-Fix

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

25.04.2013
03.10.2013
03.10.2013

9.7.