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 IC83245 Status: Geschlossen

After a crash during shutdown while truncating a log file, crash recovery
may fail due to truncated log.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
Due to a timing hole where the log file is truncated during a 
crash the LFH with the SQLPG_HFLAG2_GHCK_TRUNC_LOGFILE flag is 
not written. 
 
Errors produced in the db2diag.log should be similar to the 
following 
 
2012-03-16-04.52.29.626688-240 I2164616A373 LEVEL: Error 
PID : 373150 TID : 1 PROC : db2loggr (DB2INST1) 0 
INSTANCE: db2inst1 NODE : 000 
FUNCTION: DB2 UDB, data protection services, 
sqlpgInitRecoverable, probe:5520 
DATA #1 : <preformatted> 
Unexpected size for S0012345.LOG, PageCount 4074 ExtSize 7000 
actualFileSize 16687104
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* There is a potential for all users to hit this apar.         * 
* However, it is highly unlikely                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW version 9.5 fixpak  10                    * 
****************************************************************
Local-Fix:
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.05.2012
21.11.2012
21.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.
Problem behoben lt. FixList in der Version
9.5.0.10 FixList