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

DB2 MIGHT TRAP WHILE COMPILING A QUERY THAT IS ELIGIBLE FOR ZIGZAG JOIN
PROCESSING

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
In a rare scenario, DB2 might trap while compiling a query that 
is eligible for zigzag join processing. 
 
You will find the following in the stack trace if you encounter 
this problem: 
 
<StackTrace> 
sqloEDUCodeTrapHandler 
... 
gsignal 
abort 
... 
... 
sqlno_zzjn_generate_fact_plan 
</StackTrace>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 5                       * 
****************************************************************
Local-Fix:
You can disable zigzag join by setting 
DB2_REDUCED_OPTIMIZATION="ZZJN OFF".  You can apply this against 
an application or specific set of statements by using an 
optimization profile that contains a REGISTRY request.  You can 
also disable zigzag join by setting the optimization level to 0 
or 1.
Lösung
Problem first fixed in DB2 version 10.1 Fix Pack 5
Workaround
See Local Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.02.2015
13.07.2015
13.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList