|
Problem IT19720
|
Status: Closed |
DB2 MIGHT PRODUCE SQL0901N WHEN EXECUTING NOT EXISTS SUBQUERY WITH NESTED SUBQUERIES |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Under rare scenarios, DB2 might produce a SQL0901N error message
when the following conditions are true:
1) The query contains one or more NOT EXISTS subqueries
2) The subselect of the subquery in 1) includes one or more
subqueries
3) The nested subquery is part of a complex expression
referencing the correlated table
eg. 
select * from t1 where not exists (select * from t2 where t2.c1
= t1.c1 OR t1.c1 IN (select c1 from t3));
Stack might look like 
sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai 
sqlzeSqlCode
sqlnn_erds
sqlno_cost_subquery
sqlno_cost_subterm
sqlno_cost_subterm |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 9 or higher *
**************************************************************** |
| Local Fix: |
db2set -im DB2_ANTIJOIN=NO |
| Solution |
First fixed in Db2 10.5 Fix Pack 9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.03.2017
29.09.2017
29.09.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.
|
| Problem solved according to the fixlist(s) of the following version(s) |
