DB2 FOR LUW / DB2FORLUW / 970 - DB2

DB2 might trap with SIGSEGV during compilation of a query with 
big inlist predicate ( e.g. inlist with a few hundred elements 
): 
 
1. The table, on which the big inlist predicate is applied, has 
a generated column. 
2. There is a predicate involving the above mentioned generated 
column or its source column. 
3. There are indexes available on columns involved in predicates 
of query. 
 
The problem can happen when STMTHEAP consumption is very high 
and out-of-memory condition occurs in specific point of the 
code. 
The call-stack might look like this: 
   sorted_insert 
   sqlno_crule_index_order_plans 
   sqlno_crule_index_anding 
   sqlno_crule_access_root 
   sqlno_crule_access 
   sqlno_crule_in2join_access 
 
Or, like this: 
  sqlno_partition_index_preds 
  sqlno_btree_preds 
  sqlno_index_scan 
  sqlno_crule_index_scan 
  sqlno_crule_access_root 
  sqlno_crule_access 
 
The stack trace can vary since memory corruption can be detected 
in various place.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 11.                      * 
****************************************************************

Increase STMTHEAP to a larger value or execute the SQL statement 
at query optimization class 2 or less.

First fixed in DB2 Version 9.7 Fix Pack 11.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

07.05.2015
09.10.2015
09.10.2015

9.7.FP11