DB2 - Problem description
Problem IT19976 | Status: Closed |
SQL QUERIES WITH IN OR NOT IN CLAUSE MAY PRODUCE INCORRECT RESULTS FOR A COLUMN-ORGANIZED TABLE | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Additional space is added in rewritten query to string predicate when we use "NOT IN" clause, thus we get wrong results from query. This only happens when we have table organized by columns Example: create table t(c varchar(5)) organize by column; insert into t values('x'); select substr(c,1) from t where substr(c,1) not in (CHAR('abc'),CHAR('x')); 1 ----- x 1 record(s) selected. ==>incorrect result | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 105fp9 and higher version. * **************************************************************** | |
Local Fix: | |
Rewrite the query to avoid this condition. | |
available fix packs: | |
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows | |
Solution | |
Upgrade to DB2 105fp9 and higher version. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 31.03.2017 09.10.2017 12.10.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |