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

DB2EXPLN COMMAND WITH REOPT ALWAYS OPTION DOES NOT GIVE A MEANINGFUL OUTPUT

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When using the db2expln command with the REOPT ALWAYS option, 
the output displayed is not meaningful. 
 
Estimated Cost = 0.000000 
Estimated Cardinality = 0.000000 
 
 
End of section 
 
 
Optimizer Plan: 
 
Rows 
Operator 
(ID) 
Cost 
 
* 
/ \ 
1 54 
IXSCAN Table: 
( 3) <0,5> <<==Not real onject names. 
7.56976 
| 
54 
Index: 
<0,5,1> <<==Not real index names 
 
Solution: 
 
This section is basically a placeholder. 
 
When a package is bound with REOPT ALWAYS, it does not 
necessarily means that every statement in the package will be 
rebound every time. 
When the optimizer initially compiles the statement, it checks 
to see if the statement is a candidate for reopt processing.  If 
the statement is not a candidate, then the section stored in the 
package will be the one used during run-time. 
 
New message added will be as below 
 
"Section will be recompiled for REOPT processing."
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users before this release                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to the latest release                         * 
****************************************************************
Local-Fix:
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.06.2012
06.11.2012
06.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version