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 IT03676 Status: Closed

A QUERY MAY HIT -901 ERROR WHEN IT CONTAINS PREDICATE COL=NULL

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When a query has local equality predicate on a simple column 
"tab1.colX = NULL" as well as equality predicate "tab1.colX = 
tab2.colY" where tab1 and tab2 are two different tables or 
quantifiers, the query compilation may return -901 error 
"invalid qnc assignment" and the following compiler error stack 
can be found in db2diag.log: 
 
sqlnr_splitswbox[60] 
sqlnq_qtb::box_opr_split[116] 
sqlnq_pid::update_qnc[100] 
sqlnq_pid::replace_qnc[100] 
 
Note in Oracle compatibility mode "COL=''" is also transformed 
to "COL=NULL".
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 10.                      * 
****************************************************************
Local Fix:
Replace "COL=NULL" or "COL=''" in ORA compatibility 
mode to an always false predicate "1=0" in the query SQL 
statement.
Solution
First fixed in Version 9.7 Fix Pack 10.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.08.2014
17.11.2014
17.11.2014
Problem solved at the following versions (IBM BugInfos)
9.7.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.10 FixList