DB2 - Problem description
Problem IT02215 | Status: Closed |
INCORRECT RESULTS FROM COLUMN-ORGANIZED TABLE WHEN PREDICATE COMPARES NULL VS CAST(NULL AS <DATA_TYPE>) | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Incorrect results might be obtained from a column-organized table when the predicate compares NULL with CAST (NULL AS <DATA_TYPE>). The following is an example of the problem: Correct result: SELECT COUNT(*) FROM TABLE1 WHERE NOT NULL IN COLUMN1 AND NULL != COLUMN1; 1 ----------- 0 1 record(s) selected. Wrong result when CAST(NULL AS BIGINT) is used: SELECT count(*) FROM TABLE1 WHERE NOT NULL IN COLUMN1 AND CAST(NULL AS BIGINT) != COLUMN1; 1 ----------- 35 1 record(s) selected. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.5.0.4. * **************************************************************** | |
Local Fix: | |
Rewrite the query to not use CAST on NULL. | |
available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Solution | |
The problem is first fixed in DB2 version 10.5.0.4. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.06.2014 08.09.2014 09.04.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.4 |