|
Problem IC64549
|
Status: Geschlossen |
EXCESSIVE MESSAGES ON HADR STANDBY: "EXTENT NNNN IN LOG PATH MAY BE STALE. TRYING ARCHIVE" |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
During normal operation, a HADR Standby will attempt to access
log files from a log archive device. This should only occur in
the HADR state 'Local Catchup'. In rare cases, the HADR Standby
might try, in error, to retrieve log files well beyond entering
'Peer' state.
If this problem occurs, you will be able to observe diag.log
entries similar to the following:
2009-10-07-17.43.47.270826-420 E2005993A367 LEVEL: Event
PID : 1278018 TID : 17549 PROC : db2sysc
0
INSTANCE: testinst NODE : 000
EDUID : 17549 EDUNAME: db2hadrs (TESTDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrSetHdrState, probe:10000
CHANGE : HADR state set to S-Peer (was S-NearlyPeer)
...
2009-10-07-18.10.30.827847-420 I2041779A358 LEVEL: Warning
PID : 1278018 TID : 5213 PROC : db2sysc
0
INSTANCE: testinst NODE : 000
EDUID : 5213 EDUNAME: db2lfr (TESTDB) 0
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog, probe:600
MESSAGE : Extent 1572 in log path may be stale. Trying archive.
...
2009-10-07-18.11.15.014076-420 I2047682A358 LEVEL: Warning
PID : 1278018 TID : 5213 PROC : db2sysc
0
INSTANCE: testinst NODE : 000
EDUID : 5213 EDUNAME: db2lfr (TESTDB) 0
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog, probe:600
MESSAGE : Extent 1573 in log path may be stale. Trying archive.
. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All users in a HADR environment *
****************************************************************
* PROBLEM DESCRIPTION: *
* During normal operation, a HADR Standby will attempt *
* toaccess log files from a log archive device. This *
* shouldonly occur in the HADR state 'Local Catchup'. In *
* rarecases, the HADR Standby might try, in error, to retrieve *
* logfiles well beyond entering 'Peer' state.If this problem *
* occurs, you will be able to observe diag.logentries similar *
* to the following:2009-10-07-17.43.47.270826-420 *
* E2005993A367LEVEL:EventPID : 1278018 TID : *
* 17549 PROC:db2sysc 0INSTANCE: testinst *
* NODE : 000EDUID : 17549 EDUNAME: db2hadrs *
* (TESTDB) 0FUNCTION: DB2 UDB, High Availability *
* DisasterRecovery,hdrSetHdrState, probe:10000CHANGE : HADR *
* state set to S-Peer (was *
* S-NearlyPeer)...2009-10-07-18.10.30.827847-420 *
* I2041779A358LEVEL:WarningPID : 1278018 TID *
* : 5213 PROC:db2sysc 0INSTANCE: testinst *
* NODE : 000EDUID : 5213 EDUNAME: db2lfr *
* (TESTDB) 0FUNCTION: DB2 UDB, recovery *
* manager,sqlplfrFMOpenLog,probe:600MESSAGE : Extent 1572 in *
* log path may be stale. *
* Tryingarchive....2009-10-07-18.11.15.014076-420 *
* I2047682A358LEVEL:WarningPID : 1278018 TID *
* : 5213 PROC:db2sysc 0INSTANCE: testinst *
* NODE : 000EDUID : 5213 EDUNAME: db2lfr *
* (TESTDB) 0FUNCTION: DB2 UDB, recovery *
* manager,sqlplfrFMOpenLog,probe:600MESSAGE : Extent 1573 in *
* log path may be stale. Tryingarchive.... *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to Version 9.7 Fipak 2 or later *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem is first fixed in Version 9.7 Fixpak 2 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC66724
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 13.11.2009
22.06.2010
22.06.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.2
|
 |
