DB2 FOR LUW / DB2FORLUW / B10 - DB2

By design, dropping a column or changing its data type removes
all statistics information from the table being altered, and
Statistics must be recollected after it is again accessible.

However, it seems that ALTER TABLE is using the presence of the
latest_statsrun_offset(command "db2cat -d  -s 
-n  -o .pd" can used to dump out
latest_statsrun_offset value) as an indication of whether
statistics exist, but it won't exist if stats have been set
manually using UPDATE SYSSTAT statements(i.e. the db2look mimic
approach) instead of actually running runstats, as a result, the
statistics won't be cleaned up.

The statistics need to be cleaned up regardless of how they were
set or collected because the column alteration could mean that
the statistics are inconsistent with the data type i.e. wrong
length, wrong format etc.

****************************************************************
* USERS AFFECTED:                                              *
* n/a                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 for LUW V11.1 Mod4 Fixpack6 or later.         *
****************************************************************

Run RUNSTATS against the table to remove and collect the latest
statistics after the table is again accessible after alter table
operation.

not known / see Local fix

forerunner  : 
follow-up : IT34032 

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

25.08.2020
21.03.2021
21.03.2021