DB2 FOR LUW / DB2FORLUW / A10 - DB2

The db2look with -m option can generate the same predicates like 
as below against different indexes on the same table. 
 
WHERE COLNAMES = ' ' 
AND TABNAME = '<tabname>' AND TABSCHEMA = '<schema>'; 
 
COLNAMES is valid only if each column name is less than 30 bytes 
and if there are fewer than 16 columns in the index. Otherwise, 
the value can be blank. 
As the db2look uses COLNAMES to mimic index stats against 
primary key index and indexes for unique constraint. 
So db2look generates an invalid update statements to mimic index 
stats if a table has more than one indexes meet above 
conditions.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use db2look with -m option against unique indexes. * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V10.1 FixPack 4 or later.              * 
****************************************************************

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

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

not known / see Local fix

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

23.10.2013
02.06.2014
02.06.2014