DB2 FOR LUW / DB2FORLUW / A50 - DB2

When Rollforward hits a log that has been truncated but has a
partial log record at the end of the log, Rollforward stop will
not work (the expected behaviour is that DB2 should Rollback any
opened transactions and complete).

db2 rollforward to end of logs -
SQL1042C  An unexpected system error occurred.
SQLSTATE=58004

db2 rollforward stop  - this should allow to come out of
rollforward

Instead it will fail with either SQL1042C or SQL1273N.

db2 "rollforward db osdb stop noretrieve"
SQL1273N  An operation reading the logs on database "xxx" cannot
continue because of a missing log file "S00xxxx.LOG" on database
partition "0"
and log stream "0".

db2diag.log messages might show this kind of corruption is hit
as SQLP_BADLOG

FUNCTION: DB2 UDB, recovery manager, sqlpshrEdu, probe:45325
MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File
cannot be used"
          DIA8414C Logging can not continue due to an error.
DATA #1 : String, 66 bytes
last record from this extent does not match lastLfsLsn in its
XHDR


Note that db2cklog might not detect this kind of corruption.

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to release inclusive of this fix. See sysroute APAR. *
****************************************************************

not known / see Local fix

forerunner  : 
follow-up : IT24522 

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

25.10.2016
23.03.2018
23.03.2018