|
Problem IC78621
|
Status: Closed |
DB2EXPLN COMMAND WITH REOPT ALWAYS OPTION DOES NOT GIVE A MEANINGFUL OUTPUT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 fp 6 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Upgrade to latest fix pack |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.09.2011
17.07.2012
17.07.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
