DB2 FOR LUW / DB2FORLUW / A50 - DB2

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

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users below V10.5fp3                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to 10.5.0.3                                           * 
****************************************************************

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
 

Problem Fixed In 10.5.0.3

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

27.08.2013
04.03.2014
04.03.2014