DB2 FOR LUW / DB2FORLUW / A10 - DB2

The db2expln cannot print names for CGTTs, then prints SQL0100W 
instead. 
The following steps illustrates the problem. 
 
1. Create a CGTT 
db2 connect to sample 
db2 create global temporary table t1 like org 
 
2. Take an explain by db2expln. 
db2expln -d sample -q "select * from t1" -t 
 
The explain output shows no table name, then prints SQL0100W as 
below: 
 
(    2) Access Warning during FETCH for table. 
 
Message Text = 
SQL0100W  No row was found for FETCH, UPDATE or DELETE; or the 
result of a 
query is an empty table.  SQLSTATE=02000 
 
sqlcaid   = SQLCA 
sqlcabc   = 136 
sqlcode   = 100 
sqlstate  = 02000 
sqlerrml  = 0 
sqlerrmc  = 
sqlerrp   = SQLRI01F 
sqlerrd0  = 0x80040001 = -2147221503 
sqlerrd1  = 0x00000001 = 1 
sqlerrd2  = 0x00000000 = 0 
sqlerrd3  = 0x00000000 = 0 
sqlerrd4  = 0x00000000 = 0 
sqlerrd5  = 0x00000000 = 0 
sqlwarn   = ' ', ' ', ' ', ' ', ' ', ' ', ' ', ' ', ' ', ' ', ' 
' 
 
Global Temporary Table Name = .  ID = -6,-32768 
   // missing table schema.name 
        |  |  Prefetch: Eligible 
        |  Sargable Predicate(s) 
(    1) |  |  Return Data to Application 
        |  |  |  #Columns = 5 
(    1) Return Data Completion

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who take db2expln against SQL statements involving     * 
* CGTTs.                                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V10.1 FixPack 5 or later.              * 
****************************************************************

Please use explain option to compile the statements, then format 
it by db2exfmt tool.

This problem was first fixed in DB2 V10.1 FixPack 5.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

05.06.2014
13.07.2015
13.07.2015