DB2 FOR LUW / DB2FORLUW / 950 - DB2

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.

**************************************************************** 
* 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.                                               * 
****************************************************************

Update LOGSECOND temporarily to -1 (Infinite logging). After 
crash recovery completes, LOGSECOND can be updated back to the 
old value.

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
 

Problem is first fixed in Version 9.5 Fixpack 8

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC75591 IC75842 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

31.03.2011
01.07.2011
01.07.2011

9.5.,
9.5.FP8