Hi. During our last High Availability exercise we got the error below and then the database crashed.
We had to restore from a backup and rollforwarded the logs to get the database up again.
According to this APAR...
IC71024: PURPOSE OF THIS APAR IS TO ADD DIAGNOSTICS CODE FOR ERROR "BEING ASKED TO FORCE LOGS PAST THE CURRENT TAILLSN" IN DB2DIAG.LOG
...the message for the error has been changed to make it more clear, and it was done for v9.7 fp 7 as well.
I would like to know if there a fix for the error itself yet, and in what version. Our database is on DB2 LUW V9.5 fp4
2013-03-03-05.33.03.296670+120 I310763A573 LEVEL: Severe
PID : 15925492 TID : 18249 PROC : db2sysc 0
INSTANCE: ipeprd01 NODE : 000 DB : IPE1_PRD
APPHDL : 0-60 APPID: 10.11.5.14.48891.130302160855
AUTHID : IPEADM
EDUID : 18249 EDUNAME: db2agent (IPE1_PRD) 0
FUNCTION: DB2 UDB, data protection services, sqlpflog, probe:50
MESSAGE : Being asked to force logs past the current taillsn:
Any help will be appreciated.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.