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

THE MAX_TIME_DIFF VALUE USED DURING ROLLFORWARD IS THE VALUE IN USE AT
THE TIME OF THE BACKUP

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The MAX_TIME_DIFF value used during a rollforward operation 
is the value from the LFH file, which will be based on the value 
at the time of the backup and not the current dbm cfg parameter 
value. 
 
If sql1472 errors are returned during a rollforward operation, 
updating the dbm cfg will not increase the MAX_TIME_DIFF value 
for the rollforward. 
 
This apar will cause DB2 to use the value from the dbm cfg.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DPF Rollforward users                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The MAX_TIME_DIFF value used during a rollforward operation  * 
* is the value from the LFH file, which will be based on the   * 
* value at the time of the backup and not the current dbm cfg  * 
* parameter value.                                             * 
*                                                              * 
* If sql1472 errors are returned during a rollforward          * 
* operation, updating the dbm cfg will not increase the        * 
* MAX_TIME_DIFF value for the rollforward.                     * 
*                                                              * 
* This apar will cause DB2 to use the value from the dbm cfg.  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply v9.7.2                                                 * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
Problem is first fixed in DB2 UDB version 9.7 fix pack 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.11.2009
18.02.2010
18.02.2010
Problem solved at the following versions (IBM BugInfos)
9.7.2,
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList