DB2 - Problem description
Problem IT07861 | Status: Closed |
CORRELATED EXISTENTIAL SUBQUERIES MIGHT BE DEPICT SLOW PERFORMANCE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Under rare scenarios, DB2 might depict unoptimized query plan for queries when the following is true: 1) The query contains one or more correlated subqueries 2a) The subqueries are of the type NOT EXISTS/NOT IN 2b) Alternatively, the subqueries are of the type EXISTS() or EXISTS() 3) There are three or more tables in the outer subselect of the query. Atleast one of these tables is not correlated to the above subqueries 4) The order of the joins between the outer tables places the correlated parent table as the last join. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Platforms * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW v10.5 Fixpack 6 or Later. * **************************************************************** | |
Local Fix: | |
1) Rewrite the query to add redundant join predicates 2) Use registry variable: db2set DB2COMPOPT=ALLOW_COMPLEX_SQ | |
Solution | |
First Fixed in DB2 LUW v10.5 Fixpack 6. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.03.2015 26.08.2015 26.08.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.6 |