DB2 FOR LUW / DB2FORLUW / A50 - DB2

Incorrect entries in the db2optstat files are made of all 
indexes that had runstats executed already. 
 
In db2optstat file we can see excessive entries during execute 
runstats.. 
 
example: 
1. create table and indexes IDX_1,IDX_2,IDX_3,IDX_4 
2. runstats on IDX_1 -> entires for IDX_1 
3. runstats on IDX_2 -> entires for IDX_2,IDX_1 
4. restart 
5. runstats on IDX4 -> entires for IDX_4 and IDX_2,IDX_1 (the 
ones which had runstats already collected) 
6. runstats on IDX_3 -> entires for IDX_3 and IDX_4,IDX_2,IDX_1 
(the ones which had runstats already collected) 
 
example output: 
COLLECT : TABLE AND INDEX STATS : Object name with schema : AT 
 
"2015-04-14-11.29.51.707000" : BY "User" : success 
 
OBJECT  : Object name with schema, 19 bytes 
 
MYSCHEMA.TAB 
 
IMPACT  : None 
 
DATA #1 : String, 113 bytes 
 
RUNSTATS ON TABLE "MYSCHEMA"."TAB" FOR INDEXES 
"MYSCHEMA"."IDX_2", "MYSCHEMA"."IDX_1" UTIL_IMPACT_PRIORITY 30

**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fix Pack 7                               * 
****************************************************************

First fixed in DB2 10.5 Fix Pack 7

not known / see Local fix

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

24.06.2015
09.05.2017
09.05.2017