DB2 - Problem description
Problem IT05492 | Status: Closed |
A QUERY MAY HIT -901 ERROR WHEN IT CONTAINS PREDICATE COL=NULL | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - 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: * * Update to version 10.1 fixpack 5 * **************************************************************** | |
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 10.1 fixpack 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 11.11.2014 20.07.2015 20.07.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.5 |