DB2 FOR LUW / DB2FORLUW / 970 - DB2

The problem is caused by the conflict between the loggr and log
reader. While loggr is renaming the log (e.g. S0082405.LOG) to
another new log e.g.S0082605.LOG, the log reader is trying to
read log records from S0082405.LOG.

In v97, log files are retrieved into the active log path, where
these kind of conflicts could occur. Before the file name of
82405 is renamed into 82605 and after the extent header of
82405 is updated to 82605, the log reader retrieved 82405 and
overwrite the extent header back to 82405. Loggr noticed the
mismatch between the extent numbers and reported error.

This kind of problem would only occur in a small timing window
and will not happen in later releases (v101 and onward).

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* See SYSROUTE APARs to see where this APAR is addressed       *
****************************************************************

Restart the log reader program

not known / see Local fix

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

12.06.2016
08.05.2017
08.05.2017