DB2 FOR LUW / DB2FORLUW / A10 - DB2

For this problem to happen, ALL of the following conditions need 
to be true: 
1) An interrupt (or any possible error) is received with a 
specific timing during the execution of a query. 
2) The query in question has the following characteristics: 
a) There is a correlated subquery, where the access plan of the 
subquery contains a union operation that itself exists on the 
probe (left) side of hash join. 
b) There is a hash join inside one of the union legs. 
 
As well, this problem is much more likely to happen in DPF. 
While it's technically possible that the problem could happen in 
a non-dpf environment, it doesn't seem likely there. Further, 
there may also be other unexpected symptoms if, rather than item 
b) above, it is some other operation inside the union leg. 
 
In the case where this was discovered, a db2trc will reveal a 
hash join looping infinitely like this: 
 
1           sqlrihsjn entry [eduid 135 eduname db2agent] 
2           sqlrihsjn exit 
3           sqlrihsjn entry [eduid 135 eduname db2agent] 
4           sqlrihsjn exit 
5           sqlrihsjn entry [eduid 135 eduname db2agent] 
6           sqlrihsjn exit 
7           sqlrihsjn entry [eduid 135 eduname db2agent] 
8           sqlrihsjn exit 
9           sqlrihsjn entry [eduid 135 eduname db2agent] 
10          sqlrihsjn exit 
11          sqlrihsjn entry [eduid 135 eduname db2agent] 
12          sqlrihsjn exit 
13          sqlrihsjn entry [eduid 135 eduname db2agent] 
14          sqlrihsjn exit 
...<snip...repeating...>

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3.                      * 
****************************************************************

It may be possible to rewrite the query so to avoid the 
correlation subquery.

DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 10.1 Fix Pack 3.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC95391 
follow-up : 

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

12.06.2013
15.10.2013
15.10.2013