|
Problem IC95356
|
Status: Closed |
GRAPH GENERATED WITH 'DB2EXPLN -G' DOES NOT CONTAIN STATISTICS |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When an explain plan is generated using 'db2expln -g' command,
it does not contain the cost and the cardinality estimate for
its operators. This can be demonstrated with a simple example as
seen below:
db2expln -d sample -t -g -q "values current timestamp"
******************** DYNAMIC
***************************************
==================== STATEMENT
==========================================
Isolation Level = Cursor Stability
Blocking = Block Unambiguous Cursors
Query Optimization Class = 5
Partition Parallel = No
Intra-Partition Parallel = No
SQL Path = "SYSIBM", "SYSFUN",
"SYSPROC", "SYSIBMADM"
Statement:
values current timestamp
Section Code Page = 1208
Estimated Cost = 0.004800
Estimated Cardinality = 1.000000
Table Constructor
| 1-Row(s)
Return Data to Application
| #Columns = 1
End of section
Optimizer Plan:
Operator
(ID)
RETURN
( 1)
|
TBSCAN
( 2)
|
TFunc:
SYSIBM
GENROW |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users below V10.5fp3 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to 10.5.0.3 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
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
|
| Solution |
Problem Fixed In 10.5.0.3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2013
04.03.2014
04.03.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
