suche 36x36
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 IT22972 Status: Closed

QUERY INVOLVING OUTER JOINS HAS WRONG COLUMN RESULT NULLABILITY

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
A query involving outer joins may have the wrong column result 
nullability.  For example, the following result column should 
have type 493 (nullable BIGINT) but instead returns type 492 
(not nullable BIGINT). 
 
 
   CREATE TABLE T1 ( C1 BIGINT ); 
   CREATE TABLE T2 ( C2 BIGINT NOT NULL ); 
   CREATE TABLE T3 ( C3 BIGINT); 
 
   describe 
     SELECT T2.C2 
     FROM 
       T1 
       LEFT JOIN T2 ON 1=1 
       LEFT JOIN T3 ON 1=1 
     WHERE T2.C2 = T3.C3; 
 
    Column Information 
 
    Number of columns: 1 
 
    SQL type              Type length  Column name 
Name length 
    --------------------  ----------- 
------------------------------  ----------- 
    492   BIGINT                    8  C2 
2 
 
This only occurs when the semantics of the query dictate a 
nullable result, but - due to predicates - the query cannot 
actually produce a NULL result.  For this reason, this issue 
will rarely be noticeable.  However, it can be a problem in the 
following scenarios: 
 
- import/export: import may produce wrong results when the 
export was based on such a query 
- CREATE TABLE as query, the resulting table column will have 
the wrong nullability
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1 Fixpack 3 Mod 2 or higher                * 
****************************************************************
Local Fix:
Solution
First fixed in Db2 11.1 Fixpack 3 Mod 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.10.2017
07.08.2018
07.08.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)