home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC64883 Status: Closed

THE DB2 SERVER MAY ABEND DURING COMPILATION OF QUERIES ON RANGE PARTITIONED
TABLES WITH JOIN AND OR PREDICATES ON PARTITIONING C

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
The DB2 Query Optimizer may cause the DB2 server to abend under 
certain situations when the query being compiled contains join 
predicates and OR predicates on the range partitioning 
column(s). 
 
Either of the following stack traces can be produced if you 
encounter this error. 
 
5        sqlno_get_datapart_elim 
6        sqlno_crule_datapart_elimination 
7        sqlno_crule_access_root 
8        sqlno_crule_access 
9        sqlno_plan_qun 
10       sqlno_call_sf 
11       sqlno_each_opr 
 
or 
 
5        sqlno_datapart_conv_key 
6        sqlno_datapart_elim_compute_bitmap 
7        sqlno_datapart_key_elim 
8        sqlno_prop_compute_each_dpelim_adjustment 
9        sqlno_prop_compute_dpelim_adjustments 
10       sqlno_prop_compute_ff_partial_adjustments 
11       sqlno_prop_compute_ff_adjustments 
12       sqlno_plan_begin_opr 
13       sqlno_call_sf 
14       sqlno_each_opr
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* This applies to all users on V9.1, V9.5, V9.7                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The DB2 Query Optimizer may cause the DB2 server to          * 
* abendundercertain situations when the query being compiled   * 
* containsjoinpredicates and OR predicates on the range        * 
* partitioningcolumn(s).Either of the following stack traces   * 
* can be produced if youencounter this error.5                 * 
* sqlno_get_datapart_elim6                                     * 
* sqlno_crule_datapart_elimination7                            * 
* sqlno_crule_access_root8        sqlno_crule_access9          * 
* sqlno_plan_qun10      sqlno_call_sf11      sqlno_each_opror5 * 
*        sqlno_datapart_conv_key6                              * 
* sqlno_datapart_elim_compute_bitmap7                          * 
* sqlno_datapart_key_elim8                                     * 
* sqlno_prop_compute_each_dpelim_adjustment9                   * 
* sqlno_prop_compute_dpelim_adjustments10                      * 
* sqlno_prop_compute_ff_partial_adjustments11                  * 
* sqlno_prop_compute_ff_adjustments12                          * 
* sqlno_plan_begin_opr13      sqlno_call_sf14                  * 
* sqlno_each_opr                                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Recommend moving to latest fix pack.                         * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
Fixed in V9.1 fix pack 9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC64919 IC64920 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.11.2009
29.04.2010
29.04.2010
Problem solved at the following versions (IBM BugInfos)
9.1.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.9 FixList