DB2 FOR LUW / DB2FORLUW / 980 - DB2

Crash recovery may fail if during crash recovery, the next Log 
Sequence Number ( LSN ) is pointing to a log file that has not 
yet been allocated or is no longer available on the system. This 
condition is rare, as normally log files are pre-allocated. 
The db2diag.log will show messages like : 
 
2010-03-05-13.01.08.442116+000 I4808A363          LEVEL: Error 
PID     : 24295                TID  : 16          PROC : db2sysc 
0 
INSTANCE: db2inst3             NODE : 000         DB   : SAMPLE 
EDUID   : 16                   EDUNAME: db2loggr (SAMPLE) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpgSwitchFromRedoToUndo, 
probe:1820 
MESSAGE : File Count <= TailIndex 
 
2010-03-05-13.01.08.442614+000 I5172A168          LEVEL: Error 
PID:24295 TID:16 NODE:000 Title: SQLP_DBCB 
Dump File:/home/db2inst3/sqllib/db2dump/24295.16.000.dump.bin

**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Crash recovery failure when system is unable to              * 
* (pre)allocate log files                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* none                                                         * 
****************************************************************

DB2 Service may be able to patch the log control file to 
circumvent the code path.

keiner bekannt / siehe Local-Fix

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

18.03.2010
29.03.2011
29.03.2011