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

LOG FILE MAY GET ARCHIVED AT UNEXPECTED PATH DURING HADR FORCE TAKEOVER

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Redo phase after forced takover, may put log file at unexpected 
log chain. This can cause problem when old primary requests to 
rejoin HADR pair as a standby as it does not find log file at 
expected log chain. 
 
Here are messages dumped in new primary indication change in log 
chain for archiving logs. 
 
2012-09-27-18.11.12.048410+540 E7148849A462       LEVEL: Info 
PID     : 4653426              TID  : 4885        PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000 
EDUID   : 4885                 EDUNAME: db2logmgr (inst) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgArchiveLogFile, probe:3180 
DATA #1 : <preformatted> 
Completed archive for log file S0010494.LOG to 
/db2/inst/log_archive/db2inst/inst/NODE0000/C0000039/ from 
/db2/inst/log_dir/NODE0000/. 
 
 
2012-09-27-18.11.17.321304+540 E7149687A462       LEVEL: Info 
PID     : 4653426              TID  : 4885        PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000 
EDUID   : 4885                 EDUNAME: db2logmgr (inst) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgArchiveLogFile, probe:3180 
DATA #1 : <preformatted> 
Completed archive for log file S0010495.LOG to 
/db2/inst/log_archive/db2inst/inst/NODE0000/C4967295/ from 
/db2/inst/log_dir/NODE0000/. 
 
Now, when old primary tries to rejoin HADR, it fails to do so, 
as it can not find log file S0010495.log at expected location. 
 
 
2012-09-27-18.13.08.809540+540 I7156576A367       LEVEL: Warning 
PID     : 4653426              TID  : 5656        PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000 
EDUID   : 5656                 EDUNAME: db2lfr (inst) 0 
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog, 
probe:5120 
MESSAGE : Return code for LFR opening file S0010495.LOG was 
-2146434659 
 
 
2012-09-27-18.13.08.809943+540 I7156944A481       LEVEL: Error 
PID     : 4653426              TID  : 16193       PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000 
EDUID   : 16193                EDUNAME: db2hadrp (inst) 0 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduP, 
probe:20590 
MESSAGE : HADR primary database failed to read log pages for 
remote catchup. 
          sqlplfrScanNext returned rc = 0x860f000a, scanPages = 
0, scanFlagsOut 
          = 0x2 
 
2012-09-27-18.14.52.088747+540 I7161882A367       LEVEL: Warning 
PID     : 4653426              TID  : 5656        PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000 
EDUID   : 5656                 EDUNAME: db2lfr (inst) 0 
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog, 
probe:5120 
MESSAGE : Return code for LFR opening file S0010495.LOG was 
-2146434659 
 
2012-09-27-18.14.52.088997+540 I7162250A481       LEVEL: Error 
PID     : 4653426              TID  : 16193       PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000 
EDUID   : 16193                EDUNAME: db2hadrp (inst) 0 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduP, 
probe:20590 
MESSAGE : HADR primary database failed to read log pages for 
remote catchup. 
          sqlplfrScanNext returned rc = 0x860f000a, scanPages = 
0, scanFlagsOut 
          = 0x2
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users below Db2 v97fp8                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v97fp8                                        * 
****************************************************************
Local Fix:
Manually ship the missing log file at expected location.
available fix packs:
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Issues fixed in DB2 v97fp8
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.11.2012
05.04.2013
05.04.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.8 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.