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

DB2 MIGHT TRAP WHILE COMPILING A SQL STATEMENT CONSISTING OF MULTIPLE
TABLES JOINED ON THE PARTITION BY RANGE COLUMNS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The following is the typical stack trace produced if you 
encounter this error: 
 
sqlno_prop_adjust_ff_each_adj 
sqlno_prop_adjust_ff 
sqlno_dpart_elim_sel 
sqlno_prop_compute_each_dpelim_adjustment 
sqlno_prop_compute_dpelim_adjustments 
sqlno_prop_compute_ff_partial_adjustments 
sqlno_prop_compute_ff_adjustments 
sqlno_plan_begin_opr 
 
The problem is rare; it was observed to occur when the SQL 
statement consists of a large number of range partitioned tables 
joined on the partition by range columns, and IN predicates with 
a list of values on those columns as well.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V10.1 on LUW users.                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fix Pack 4 or above.                    * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Fixed in DB2 V10.1 Fix Pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.12.2013
11.06.2014
11.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList