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

ONLINE BACKUP FAILS DUE TO BAD FIRSTLOS AFTER TAKEOVER

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2 online backup fail due to bad firstlso 
 
db2diag.log shows: 
 
2013-04-14-11.00.47.392831-240 I16024E572          LEVEL: Severe 
PID     : 25065                TID  : 46912895969600PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 26                   EDUNAME: db2loggw (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, sqlpgWriteToDisk, 
probe:909 
MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File 
cannot be used" 
          DIA8414C Logging can not continue due to an error. 
DATA #1 : <preformatted> 
diffPage 4525697760966550 TailPage 0 does not match pagePso 
9479596405913 and firstLso 9479606295714
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB1 v10.1 FixPack 4 or later                      * 
****************************************************************
Local Fix:
N.A
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 v10.1 FixPack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.09.2013
26.06.2014
26.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList