home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC71024 Status: Geschlossen

PURPOSE OF THIS APAR IS TO ADD DIAGNOSTICS CODE FOR ERROR "BEING ASKED
TO FORCE LOGS PAST THE CURRENT TAILLSN" IN DB2DIAG.LOG

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Main purpose of this APAR is to add more diagnostics code to 
provide more information regarding error "Being asked to force 
logs past the current taillsn" seen in db2diag.log.  This 
message subsequently causes database crash. 
 
Example entry of this message is as below: 
 
2009-11-06-05.01.45.918671+000 I9058A458          LEVEL: Severe 
PID     : XXXXXX            TID  : XXXX        PROC : db2sysc 0 
INSTANCE: XXXXXXXX          NODE : XXX 
EDUID   : XXXX              EDUNAME: db2pclnr (WPTS) 0 
FUNCTION: DB2 UDB, data protection services, sqlpflog, probe:50 
MESSAGE : Being asked to force logs past the current taillsn: 
 
The page cleaner calls the sqlpflog() with a bad LSN value which 
is much higher than the last LSN generated for this database. 
This is logically incorrect and hence causes database to crash. 
 
Additional diagnostics will provide more information to debug 
this error and the crash. Please note that this APAR does not 
prevent the actual crash.
Problem-Zusammenfassung:
USERS AFFECTED: 
=============== 
Customer using version 9.1 and above on all platforms. 
 
PROBLEM DESCRIPTION: 
==================== 
Please note that this APAR does not prevent the crash caused by 
the error "Being asked to force logs past the current taillsn". 
The purpose of this APAR is only to add code that will generate 
addtional diagnostics when this error occur.
Local-Fix:
verfügbare FixPacks:
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 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

Lösung
Problem is first fixed in version 9.7 Fixpack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
08.09.2010
03.05.2011
03.05.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList