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

BACKWARD PHASE OF ROLLFORWARD RECOVERY CAN BE VERY SLOW

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
During the backward stage of rollforward recovery - after either 
a system crash or during rollforward after a restore then DB2 
can repeatedly request the same two log files alternately.  This 
leads to the rollforward being extremely slow. 
In the db2diag.log the repeated requests for the same logs are 
recorded , eg : 
 
$ grep retrieve db2diag.log 
 
db2diag.log:MESSAGE : Started retrieve for log file 
S0000008.LOG. 
db2diag.log:MESSAGE : Completed retrieve for log file 
S0000008.LOG on chain 0 to 
db2diag.log:MESSAGE : Started retrieve for log file 
S0000009.LOG. 
db2diag.log:MESSAGE : Completed retrieve for log file 
S0000009.LOG on chain 0 to 
db2diag.log:MESSAGE : Started retrieve for log file 
S0000008.LOG. 
db2diag.log:MESSAGE : Completed retrieve for log file 
S0000008.LOG on chain 0 to 
etc 
 
 
The db2pd -recovery option will also show very slow bytes/second 
in backward 
phase of rollforward recovery. 
 
 
The problem is not platform specific.  The occurrence of the 
problem is chance dependent on whether a data buffer crosses two 
logfiles. 
The problem exists in the 9.5 and 9.7 codestreams.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.5 FP7 or later                             * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
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

Lösung
Problem first fixed in DB2 V9.5 FP7
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC70815 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
23.08.2010
20.01.2011
20.01.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP7
Problem behoben lt. FixList in der Version
9.1.0.7 FixList
9.5.0.7 FixList