|
Problem IC64920
|
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 / 970 - 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: *
* 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: *
* Upgrade to Fix pack 2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.12.2009
25.05.2010
25.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
