home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC99808 Status: Closed

DB2 MIGHT PRODUCE SQL0901N WHEN EXECUTING NOT IN QUERY WITH CORRELATED
SUBSELECT

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
DB2 might produce SQL0901N when the following conditions are 
true: 
1. There is a NOT IN subquery 
2. The NOT IN subquery contains one or more scalar subqueries 
which have correlation 
3. The parent of the NOT IN subquery, i.e. the column on which 
NOT IN predicate is applied is nullable 
4. There is another table in the query which is joined to the 
parent table 
 
eg. 
create table X(col1 int, col2 int); <--------- condition 3 
 
SELECT 
col1 
FROM 
X,  <-------------- parent table 
Y   <-------------- condition 4 
WHERE 
X.col1 = Y.col1 AND 
X.col1 NOT IN (         <----------------- condition 1 
        SELECT 
        col1 
        FROM 
        A, D 
        WHERE 
        A.col2 = D.col2 AND 
        A.col3 = D.col3 AND 
        D.col4 = (  SELECT   <----------------- condition 2 
                         MAX(col4) 
                         FROM  E 
                         WHERE 
                         E.col2 = D.col2  ) 
        ); 
 
The stack trace might be as follows: 
0        ossDumpStackTraceInternal 
1        ossDumpStackTraceV98 
2        OSSTrapFile::dumpEx 
3        sqlo_trce 
4        sqloDumpDiagInfoHandler 
5        __invoke_dynamic_linker__ 
6        pthread_kill 
7        sqloDumpEDU 
8        sqldDumpContext 
9        sqlrr_dump_ffdc 
10       sqlzeDumpFFDC 
11       sqlzeSqlCode 
12       sqlnn_erds 
13       sqlng_build_INDX_key                    ---->>> 
SQL0901N 
14       sqlng_build_KEY_obj 
15       sqlng_build_INDX_obj
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All db2 v10.5 users                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.5 fp4 or higher                           * 
****************************************************************
Local Fix:
db2set DB2_ANTIJOIN=YES
available fix packs:
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

Solution
Fixed in DB2 v10.5 fp4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.03.2014
15.09.2014
15.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList