DB2 - Problembeschreibung
Problem IC79108 | Status: Geschlossen |
DB2EXPLN COMMAND WITH REOPT ALWAYS OPTION DOES NOT GIVE A MEANINGFUL OUTPUT | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - 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: * * User on db2 v9.5 fixpack 6a AIX v5.3 * **************************************************************** * PROBLEM DESCRIPTION: * * db2explan incorrect output with the REOPT ALWAYS option * **************************************************************** * RECOMMENDATION: * * This issue is being fixed in 9.5 latest fix pack * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows | |
Lösung | |
This issue is being fixed in 9.5 latest fix pack | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC84818 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 07.10.2011 13.03.2012 13.03.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5. | |
Problem behoben lt. FixList in der Version | |
9.5.0.9 |