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

SELECT STATEMENT AGAINST AN RCT TABLE WITH A "IS NOT NULL"
PREDICATE MAY CRASH.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The following is a repro of the trap: 
 
create table t1 (a int not null) organize by key sequence (a 
starting from 1 ending at 100) disallow overflow; 
create table t2 (a int); 
insert into t1(a) values 1,2,3,4,5,6,7,8,9,10; 
insert into t2(a) values 1,2,3,4,5,6,7,8,9,10; 
 
select * from t1,t2 where t1.a=t2.a and t2.a is not null;
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users running v9.5 or later release on platforms Linux, UNIX * 
* and Windows                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 Fix Pack 2.                          * 
****************************************************************
Local Fix:
Not available.
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.1 Fix Pack 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.07.2012
31.12.2012
31.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList