DB2 FOR LUW / DB2FORLUW / B10 - DB2

During the forward phase of crash recovery and/or ROLLFORWARD
DATABASE processing, index corruption might be introduced if
following conditions are true:
- The index is compressed.  By default, index compression is
enabled for compressed tables, and disabled for uncompressed
tables.  You can override this default behavior by using the
COMPRESS YES option of the CREATE INDEX statement.
- The index is created on at least one variable length column
(i.e. VARCHAR, VARGRAPHIC, or VARBINARY).
- The variable length indexed column was altered to a longer
maximum length using the ALTER COLUMN option of the ALTER TABLE
command and this change was redone by recovery processing.

The INSPECT command, when run with INDEX NORMAL and INDEXDATA
options, can be used to detect if your system is affected.

****************************************************************
* USERS AFFECTED:                                              *
* COMPRESSED INDEX                                             *
* AND RECOVERY PROCESSING                                      *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description and install this fix.                  *
****************************************************************
* RECOMMENDATION:                                              *
* See Error Description and install this fix.                  *
****************************************************************

If index corruption or an index-data mismatch is detected,
rebuild the affected indexes.

To avoid hitting the problem see the REORG INDEXES command or
the DROP INDEX and CREATE INDEX commands to rebuild any
compressed indexes on variable length columns after increasing
the maximum length.

not known / see Local fix

forerunner  : IT24347 
follow-up : 

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

19.03.2018
20.03.2018
20.03.2018