home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT02136 Status: Closed

DATABASE ROLLFORWARD OR HADR STANDBY REPLAY FAILS WITH A LOG CHAIN ERROR
AFTER RESTORING FROM AN ONLINE BACKUP.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Database rollforward or hadr standby replay can fail with a log 
chain error and the messages sqlplfrIsLogFromValidChain, probe 
2103 and 2302 will appear in the db2diag.log file.  This is only 
an issue if the database was restored from an online backup that 
was created on a new hadr primary that recently performed a 
forced takeover which encountered tablespace I/O errors 
(sqlpForwardRecovery, probe 2610 reports error SQLP_TRCVIOERR).
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply DB2 Version 10 Fixpack 4                               * 
****************************************************************
Local Fix:
After a forced takeover completes, check for a message from 
sqlpForwardRecovery, probe 2610 reporting error SQLP_TRCVIOERR 
in the db2diag.log.  If the message appears in the db2diag.log, 
then the above issue can be avoided by deactivating and 
activating the database before the next online backup image is 
produced
Solution
Apply DB2 Version 10 Fixpack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.05.2014
08.09.2014
08.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList