DB2 - Problembeschreibung
Problem IC87721 | Status: Geschlossen |
LOG FILE MAY GET ARCHIVED AT UNEXPECTED PATH DURING HADR FORCE TAKEOVER | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Lösung | |
Issues fixed in DB2 v97fp8 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 01.11.2012 05.04.2013 05.04.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP8 | |
Problem behoben lt. FixList in der Version | |
9.7.0.8 |