|
Problem IC75842
|
Status: Geschlossen |
CRASH RECOVERY MAY HANG AFTER REACHING LOG FULL CONDITION |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problembeschreibung: |
During a log full condition, if the instance is abruptly
shutdown, on restart the database needs to go through Crash
recovery. Crash recovery may hang when it reaches the
(LOGPRIMARY + LOGSECOND) number of logs and have no further logs
to write the backward phase log records. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* During a log full condition, if the instance is abruptly *
* *
* shutdown, on restart the database needs to go through Crash *
* *
* recovery. Crash recovery may hang when it reaches the *
* *
* (LOGPRIMARY + LOGSECOND) number of logs and have no further *
* logs *
* to write the backward phase log records. *
****************************************************************
* RECOMMENDATION: *
* included in v91fp11 *
**************************************************************** |
| Local-Fix: |
Update LOGSECOND temporarily to -1 (Infinite logging). After
crash recovery completes, LOGSECOND can be updated back to the
old value. |
| verfügbare FixPacks: |
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Lösung |
|
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 15.04.2011
07.12.2011
07.12.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.1.FP11
|
| Problem behoben lt. FixList in der Version |
| 9.1.0.11
|
 |
