|
Problem IT35377
|
Status: Closed |
WRONG RESULT IN A VERY SPECIFIC PLAN/SPECIFIC DATA FLOW WITH NLJN AND DATAPART TABLE ON THE INNER AND NULL KEYS.
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
We could loose a row in the result set in a very rare scenario:
- data partitioned table on the inner of NLJN
- NULL key values coming from the outer of NLJN first
- good key that needs a match comes from the outer right after
all the NULL keys
It is a very rare scenario which depends on a very rare plan as
well as a rare data flow. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2_v115m5fp1 or later *
**************************************************************** |
| Local Fix: |
Change query/plan to avoid NLJN or flip the sides of NLJN in the
plan using OPTGUIDELINES. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2_v115m5fp1 or later *
**************************************************************** |
| Comment |
Upgrade to db2_v115m5fp1 or later |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.12.2020
31.03.2021
31.03.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
