home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC66966 Status: Closed

CRASH RECOVERY FAILURE IN SQLPGSWITCHFROMREDOTOUNDO, PROBE:1820 WITH
MESSAGE : "FILE COUNT <= TAILINDEX"

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Crash recovery may incorrectly fail with a message saying    * 
* File Count <= TailIndex                                      * 
* There is no preventative measures for this apar, although    * 
* the conditions to encounter this problem are rare.           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the db2 server code to Fix Pack <x>                  * 
****************************************************************
Local Fix:
DB2 Service may be able to patch the log control file to 
circumvent the code path.
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
The problem will be fixed in V9.7 Fix Pack k <x>
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67307 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.03.2010
10.06.2010
10.06.2010
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList