home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IT04085 Status: Closed

WRONG RESULTS RECEIVED FOR A QUERY DUE TO INCORRECT INTERNAL COLUMN
STRUCTURES

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The wrong result set may be outputted if the Optimizer chooses 
an Explain Plan with the following characteristics: 
- HSJN has an NLJN in the Outer 
- The NLJN has another HSJN in it's Inner 
- The second, HSJN also has an NLJN in it's Outer: 
 
                                               HSJN( A) 
                                                     | 
            --------------------------------------------------- 
           | 
        NLJN(B) 
      /           \ 
                 <   other Lolepops like TEMP, etc> 
                   | 
                HSJN(C) 
                   | 
          ------------------ 
         | 
       NLJN(D) 
 
In a rare case, internal Optimization could create wrong 
internal structures and the Column coming from HSJN(C) Payload 
could return the same value as the last value that was processed 
in HSJN(C).
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.5.                             * 
****************************************************************
Local Fix:
To avoid the problem, execute the following command and then 
recycle the instance: 
db2set DB2_TCG_DEFAULT_OPTIONS="set disable_pushdown on"
Solution
The problem is first fixed in DB2 version 10.1.0.5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.08.2014
10.07.2015
10.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList