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

WRONG RESULTS AGAINST COLUMN ORGANIZED TABLE ARE POSSIBLE WITH EXPANDING
JOIN PLAN

product:
DB2 FOR LUW / DB2FORLUW / B10 - 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 11.1 Mod 2 Fix Pack 2 or higher               * 
****************************************************************
Local Fix:
Please, install this fix
available fix packs:
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in DB2 11.1 Mod 2 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.11.2016
23.06.2017
23.06.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)