home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT05492 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
Lösung
First fixed in version 10.1 fixpack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.11.2014
20.07.2015
20.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList