DB2 - Problem description
Problem IC98655 | Status: Closed |
SUBQUERIES REFERENCING AN ALWAYS FALSE PREDICATE MIGHT NOTICE BAD PERFORMANCE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
Under rare scenarios, a query executing on DB2 might take a long time if the following conditions are true: 1) The query contains one or more subqueries of the type NOT EXISTS/NOT IN. 2) The subqueries contains predicates which can be proven to be ALWAYS FALSE and produce an empty result set. eg. Select * from T1 Where Not Exists (select * from T2 where T1.c1 = T2.c1 and 1=0) | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.1 fixpack 4 * **************************************************************** | |
Local Fix: | |
Workaround: 1) Manually rewrite the query to remove the subquery 2) db2set -im DB2_ANTIJOIN=NO | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Upgrade to DB2 version 10.1 fixpack 4 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC98750 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.01.2014 02.06.2014 02.06.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.4 |