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 IC81709 Status: Geschlossen

AN IN PREDICATE WITH ALL ARGUMENTS BEING CONSTANTS TOGETHER WITH AN
EQUALITY PREDICATE OF THE SAME COLUMN MAY RETURN AN ERROR

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
DB2 may return an internal error SQL0901N or in some cases, the 
DB2 instance suspended with SQL1224N in a query with IN 
predicate (from the original query or internally generated) with 
constants and an equality predicate on the same 
column as the example below: 
 
<col> IN (<constant1>, <constant2>, ...) 
AND 
<col> = <constant1> 
 
Most of the cases, the two predicates are optimized in DB2 to a 
more optimal form. In some complex scenarios where the two 
predicates are not optimized, it can result in SQL0901N error. 
 
This problem first occurs in DB2 version 9.7 Fix Pack 5 with the 
Query Optimization Class 5. 
 
If the DB2 instance is suspended (crashed) with SQL1224 the 
stack from the trap file may be similar to one of the following 
stacks.  The DB2 instance crash occurs more frequently on the 
Linux and Windows platforms. 
 
sqlno_dam_required 
sqlno_crule_access_root 
qlno_crule_access 
sqlno_crule_in2join_access 
sqlno_plan_end_opr 
sqlno_call_sf 
sqlno_each_opr 
 
OR 
 
<sqlno_crule_access_root> 
<sqlno_crule_access> 
<sqlno_crule_in2join_access> 
<sqlno_plan_end_opr> 
<sqlno_each_opr> 
<sqlno_walk_qun> 
 
OR 
 
<sqlno_get_best_plan> 
<sqlno_crule_in2join_access> 
<sqlno_plan_end_opr> 
<sqlno_each_opr> 
<sqlno_walk_qun>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 6 or later               * 
****************************************************************
Local-Fix:
Use the query optimization to any classes except 5 to avoid this 
problem.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem fixed starting DB2 Version 9.7 Fix Pack 6
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.02.2012
27.06.2012
24.09.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList