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 IC70815 Status: Closed

BACKWARD PHASE OF ROLLFORWARD RECOVERY CAN BE VERY SLOW

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* PRoblem Description: see Descripton above                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 V9.7 FP4 or later                             * 
****************************************************************
Local Fix:
available fix packs:
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

Solution
Problem is first fixed in Db2 V9.7 FP4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2010
18.05.2011
18.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList