|
Problem IT17679
|
Status: Closed |
WRONG RESULTS AGAINST COLUMN ORGANIZED TABLE ARE POSSIBLE WITH EXPANDING JOIN PLAN |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
WRONG RESULTS AGAINST COLUMN ORGANIZED TABLE ARE POSSIBLE WITH
EXPANDING JOIN PLAN, if
- Join is between 3 or more column organized tables, using
equality predicates
- top most join in the plan is happening on a variable string
value and we do find and strip trailing blanks as part of
normalization processing in preparation for join
Example:
3) HSJOIN: (Hash Join)
Cumulative Total Cost: 58882.1
Cumulative CPU Cost: 8.86042e+08
Cumulative I/O Cost: 11664
Cumulative Re-Total Cost: 58882.1
Cumulative Re-CPU Cost: 8.86042e+08
Cumulative Re-I/O Cost: 11664
Cumulative First Row Cost: 58882.1
Estimated Bufferpool Buffers: 181
Arguments:
---------
EARLYOUT: (Early Out flag)
NONE
SEMIJOIN: (Semi-join flag)
FALSE
Predicates:
----------
5) Predicate used in Join,
Comparison Operator: Equal (=)
Subquery Input Required: No
Filter Factor: 7.87278e-05
Predicate Text:
--------------
(VARCHAR(Q2.COLUMN1, 12) = Q3.COLUMN2) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 9 or higher *
**************************************************************** |
| Local Fix: |
Please, install this fix |
| Solution |
First fixed in Db2 10.5 Fix Pack 9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.10.2016
29.09.2017
12.10.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.
|
| Problem solved according to the fixlist(s) of the following version(s) |
