|
Problem IT24193
|
Status: Closed |
INTERMITTENT WRONG RESULTS ARE POSSIBLE WITH A PLAN WHERE COLUMNAR EARLY OUT NLJN IS PRESENT
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
If Columnar tables are involved in the query,
and Plan has Nested Loop Join,
and NLJN is done in Columnar processing (under CTQ lolepop),
and Nested Loop Join is marked EARLYOUT, then
it is possible, intermittently, to lose some of the rows in the
result set.
example of the early-out NLJN in the plan:
12) NLJOIN: (Nested Loop Join)
....
Arguments:
---------
EARLYOUT: (Early Out flag)
LEFT |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher *
**************************************************************** |
| Local Fix: |
change the plan to move NLJN from Columnar processing (under CTQ
lolepop) to Rowstore processing(above CTQ lolepops)
using OPTGUIDELINES |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.02.2018
27.11.2018
27.11.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
