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

A QUERY MAY COMPILE INDEFINITELY IF CERTAIN CONDITIONS ARE SATISFIED.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
In V9.1 a query may compile indefinitely if the following condit 
ions are satisfied: 
1) There are atleast two UNION ALLs joining indirectly through o 
ne or more tables 
2) One of the UNION ALL has a correlated column to either the 
table or the other UNION ALL. 
Force application is not effective in V9.1 while executing in 
this function. On ending the db2 instance, the following stack 
trace might be observed: 
sqlnr_sort_sips_order 
sqlnr_sort_sips_order 
sqlnr_sips_order 
sqlnr_magic_action 
sqlnr_comp 
sqlnr_seq 
sqlnr_rcc 
sqlnr_magic_detail_action 
sqlnr_comp 
sqlnr_seq 
sqlnr_rcc 
sqlnr_endqtb_action 
sqlnr_comp 
sqlnr_seq 
sqlnr_rcc 
sqlnr_start_action 
sqlnr_comp 
sqlnr_seq 
sqlnr_rcc 
sqlnr_exe 
sqlnn_cmpl
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All customer having UNION ALL views withcorrelated           * 
* predicates                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A QUERY MAY COMPILE INDEFINITELY IF THERE IS A UNION ALLVIEW * 
* WITH BRANCHES HAVING CONFLICTING CORRELATED PREDICATES.      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 Version 9.7 Fix  Pack 2                * 
****************************************************************
Local-Fix:
A possible work around is SET CURRENT OPTIMIZATION LEVEL to 0 
or 1.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 Version 9.7 Fix Pack 2
Workaround
A possible work around is SET CURRENT OPTIMIZATION LEVEL to 0 
or 1.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.08.2009
25.05.2010
25.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.,
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList