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

FORCING APPLICATION CAN TAKE A LONG TIME TO TAKE EFFECT WHEN OPTIMIZER
COMPILES A COMPLEX QUERY USING GREEDY JOIN ENUMERATION

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
"FORCE APPLICATION" command can take a long time to take effect 
when DB2 optimizer is compiling a complex query using greedy 
join enumeration method. Complex queries refer to queries that 
have a lot of table joins (for example, more than 30 tables) in 
one query block. 
 
 
If "FORCE APPLICATION" command doesn't take effect for a long 
time (for example, more than 5 minutes) for an application, you 
can dump the associated DB2 agent's stack. If the stack contains 
function "sqlno_crule_join", then DB2 optimizer is in the 
process of join enumeration (either dynamic programming or 
greedy). 
 
 
The following are some common scenarios of when greedy join 
enumeration is used. Note that this is not a complete list. 
 
- when optimization class is 0, 1, or 2 
- when stmtheap size is too small to complete dynamic 
programming join enumeration 
- when DB2_REDUCED_OPTIMIZATION registry variable is set to a 
number and some additional conditions are satisfied. Please 
refer to DB2 InfoCentre for the conditions.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 3                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 10.5 Fix Pack 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
05.06.2014
15.09.2014
15.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList