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

SAP: POOR PERFORMANCE WHEN SAP MEMORY TABLE IN JOIN ON COLUMN ORGANIZED
TABLES

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Db2 query may show poor performance, when the following 
conditions are met: 
 
1. The query has Left/Right Outer join 
2. There is a join between SAP memory table and tuple preserving 
side of the Outer Join 
3. Outer join is on Column organized tables 
 
Example: 
 
SELECT *FROM ( t1 LEFT OUTER JOIN t2 ON t1.c1 = t2.c1 ), 
TABLE( SAPTOOLS.MEMORY_TABLE( CAST( ? AS BLOB( 2G )) ) 
CARDINALITY 1 ) AS "t_00" ( "C_0" INTEGER ) 
WHERE t1.c2 = "t_00"."C_0" ; 
 
t1 and t2 are column organized tables in the above query.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher               * 
****************************************************************
Local Fix:
available fix packs:
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 3 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.09.2017
19.03.2018
19.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)