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

ENHANCE DIAGNOSTICS FOR "ROLLFORWARD IS NOT ABLE TO REACH THE END OF
ONLINE BACKUP" ERROR.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Following error could be encountered in DB2 HADR environment: 
=========================================== 
2013-10-01-01.01.01.123456+789 I123456A789        LEVEL: Error 
PID     : 12345678             TID  : 12345       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
APPHDL  : 0-10                 APPID: *LOCAL.DB2.131001010101 
EDUID   : 12345                EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, recovery manager, sqlprDoForwardPhase, 
probe:770 
DATA #1 : <preformatted> 
Rollforward is not able to reach the end of online backup (or 
split mirror), nextLso 30000000000 LastRecLsoLFH 4000000000 
=========================================== 
This could happen during "TAKEOVER HADR" command or "rollforward 
database" phase. 
 
Currently DB2 doesn't have enough diagnostic data to identify 
root cause of the failure. The purpose of the APAR is adding 
some code to dump more diagnostic data when the problem happens. 
 
Applying the APAR will help get more diagnostic data for root 
cause analysis, but it will not fix the error.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1.0.5                              * 
****************************************************************
Local Fix:
N/A
Solution
Problem was first fixed in DB2 UDB version 10.1 fix pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.06.2014
20.07.2015
20.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList