DB2 FOR LUW / DB2FORLUW / A50 - DB2

An instance might abend or return incorrect results under some 
very specific access plan conditions. 
 
A typical trap file might show the following functions at the 
top of the stacktrace report: 
 
sqlriREBAL2 
sqldEvalDataPred 
sqldReadTemp 
sqldfrd 
sqldRowFetch 
sqlsfetc 
sqlriFetch 
sqlriNljnNonPiped 
sqlrihsjn 
sqlriSectInvoke 
 
The problem is due to an incorrect buffer location that is being 
accessed.  This can only be confirmed by db2 service personnel 
by examining the "section dump" of the execution plan.  The 
"section dump" is located in the binary dump file. 
 
From an access plan point of view, at least the following 
conditions must be true: 
- There is a star join that has a join of a dimension table 
above the IXAND operator that references the same columns of the 
dimension table that was already accessed in the star join below 
the IXAND operator.  This might also be referred to as a back 
join. 
- The dimension table column that is accessed in the star join 
and also later used in the back join is accessed by the Data 
Sargable Predicate and the column.  The dimension table column 
must also not be added to the Output Stream of the Table Scan.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.4.                             * 
****************************************************************

There is no known workaround for this problem other than to 
force a different access plan to avoid at least one of the above 
conditions.

DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

The problem is first fixed in DB2 version 10.5.0.4.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC97773 IC97774 IC97775 IC97776 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

29.10.2013
08.09.2014
07.04.2015