|
Problem IC85718
|
Status: Closed |
QUERY MIGHT FAIL WITH SQL0901N DUE TO PRESENCE OF NICKNAME AND NOT EXISTS PREDICATE |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Under rare scenarios, DB2 might give a SQL0901N error message if
the following conditions are true:
1. There is a federated server
2. There query references one or more nick name tables
3. The query has one or more not exists predicates
Eg.
Failing query:
select c.col1, c.col2
from N1 c,
<----- nick name
T2 b
where NOT EXISTS(SELECT col1 FROM T1 a WHERE a.col1=b.col3)
<----- not exists
and c.col1 = b.col2;
SQL0901N The SQL statement or command failed because of a
database system
error. (Reason "Column number out of range".) SQLSTATE=58004 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 version 101 fix pack 2 *
**************************************************************** |
| Local Fix: |
workaround is to set DB2_ANTIJOIN=NO;
db2set DB2_ANTIJOIN=NO -im;
No need to recycle the db2 instance |
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
|
| Solution |
Fixed in DB2 version 101 fix pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.08.2012
29.01.2013
29.01.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
