DB2 FOR LUW / DB2FORLUW / B10 - DB2

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

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 2 Fix Pack 2 or higher               *
****************************************************************

db2set -im DB2_ANTIJOIN=NO

not known / see Local fix

forerunner  : IT19720 
follow-up : 

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

04.08.2017
24.10.2017
24.10.2017