|
Problem IC75461
|
Status: Closed |
CRASH RECOVERY MAY HANG AFTER REACHING LOG FULL CONDITION |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - 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 users 9.5 FP7 or earlier *
****************************************************************
* PROBLEM DESCRIPTION: *
* CRASH RECOVERY MAY HANG AFTER REACHING LOG FULL CONDITION *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to 9.5 Fixpack 8 or later containing the fix *
* for this APAR *
* OR *
* Update LOGSECOND temporarily to -1 (Infinite logging). After *
* crash recovery completes, LOGSECOND can be updated back to *
* the old value. *
**************************************************************** |
| 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.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem is first fixed in Version 9.5 Fixpack 8 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC75591 IC75842
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 31.03.2011
01.07.2011
01.07.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.,
9.5.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
