|
Problem IC75591
|
Status: Closed |
CRASH RECOVERY MAY HANG AFTER REACHING LOG FULL CONDITION |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| 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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 users *
****************************************************************
* 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: *
* Use the Local Fix or upgrade to a Fix Pack containing the *
* Fix. *
**************************************************************** |
| Local Fix: |
Update LOGSECOND temporarily to -1 (Infinite logging). After
crash recovery completes, LOGSECOND can be updated back to the
old value. |
| available fix packs: |
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 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 |
Problem has been first fixed in version 9.7 Fix Pack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.04.2011
13.12.2011
13.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
