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 IT05210 Status: Closed

HADR STANDBY DATABASE MARKED BAD WITH SQLPREPLAYMASTER, PROBE:2500
SQLP_TRECOVF

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
A standby might fail with the following entries in the 
db2diag.log when running Loads on the Primary: 
 
FUNCTION: DB2 UDB, recovery manager, sqlpReplayMaster, 
probe:2500 
RETCODE : ZRC=0x80100078=-2146434952=SQLP_TRECOVF 
          "Recovery process failed. used by BSU only.  Active 
cursor on drop table" 
          DIA8131C Roll forward recovery failed, LSN was "". 
 
MESSAGE : ADM14001C  An unexpected and critical error has 
occurred: 
          "DBMarkedBad". The instance may have been shutdown as 
a result. 
          "Automatic" FODC (First Occurrence Data Capture) has 
been invoked and 
          diagnostic information has been recorded in directory 
 
The database will get marked bad and as a result the standby 
will have to be restored from a Primary backup as it will not be 
possible to continue the rollforward
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v10.5 Fixpack 7 or Later.                 * 
****************************************************************
Local Fix:
Solution
First Fixed in DB2 LUW v10.5 Fixpack 7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.10.2014
14.01.2016
19.04.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList