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

INCORRECT RESULTS FROM COLUMN ORGANIZED TABLE WHEN WHERE CLAUSE HAS
"OR (<COL_NAME> IS NOT NULL AND <COL_NAME> IS NOT
NULL)"

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
An incorrect number of rows might be returned by DB2 when 
querying a column-organized table with a WHERE clause that 
contains "OR (<COL_NAME> IS NOT NULL AND <COL_NAME> IS NOT 
NULL)".  The following is an example of such a query: 
 
SELECT Q2.DT1 AS "C5993" 
FROM KINGFISHER.TABLE452 AS Q2 
WHERE ( 
 ( 
   (( 
       (Q2.DT1 > '2945-08-23') AND (Q2.DT1 < '3033-03-05') 
     ) AND (Q2."Small 5" >= 21014)) AND (Q2."Small 5" <= 25361 
    )) 
 OR 
  (Q2.BVC10 IS NOT NULL AND Q2.BVC10 IS NOT NULL) 
);
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.4.                             * 
****************************************************************
Local Fix:
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 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       :
23.05.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 FixList