DB2 FOR LUW / DB2FORLUW / 970 - DB2

When a DB2 database is upgraded to Version 9.7 the database 
manager may create a corrupted Log Control File 
(SQLOGCTL.LFH.1/2) during the upgrade procedure. 
 
This issue causes garbage entries in the "log truncation array" 
used internally to track log chains. 
 
A typical symptom is that ONLINE BACKUPS can not be taken 
anymore because log file(s) that have to be included are 
rejected by mistake, as shown below: 
 
2009-07-03-12.09.48.938673+120 I4238623A423       LEVEL: Warning 
PID     : 2515                 TID  : 2199375571280PROC : 
db2sysc 0 
INSTANCE: db2                  NODE : 000 
EDUID   : 22                   EDUNAME: db2lfr (XXXXXX) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpValidateLogCID, 
probe:30 
DATA #1 : <preformatted> 
extentNum 1543 extentCID 1246511573 truncArray[21] has 
extentNumber 1110946161 curCID 1110779043 
 
2009-07-03-12.09.48.938972+120 I4239047A379       LEVEL: Error 
PID     : 2515                 TID  : 2199375571280PROC : 
db2sysc 0 
INSTANCE: db2                  NODE : 000 
EDUID   : 22                   EDUNAME: db2lfr (XXXXXX) 0 
FUNCTION: DB2 UDB, recovery manager, sqlplfrIsLogFromValidChain, 
probe:5160 
DATA #1 : <preformatted> 
Log extent 1543 not in chain, rc -2045771753 
 
Online backups with the INCLUDE LOGS option fail with the 
following error message: 
 
SQL2428N The BACKUP did not complete because one 
or more of the requested log files could not be retrieved.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 9.7 GA users who migrated from a previous version.   * 
* You are still vulnerable if you migrated from a previous     * 
* version to DB2 9.7 GA and then upgrade to a later fix pack.  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If you migrated to DB2 9.7 GA, you will most likely          * 
* encounter this issue.   The fix for this issue was           * 
* introduced in DB2 9.7 FP1.  Thus to avoid the issue you must * 
* migrate directly to DB2 9.7 FP1 or a later fix pack without  * 
* migrating to DB2 9.7 GA first.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Migrate directly to 9.7 FP1 or a later fix pack without      * 
* using DB2 9.7 GA.                                            * 
****************************************************************

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
 

First fixed in DB2 Version 9.7 Fix Pack 1

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

07.07.2009
01.12.2009
25.10.2011

9.7.,
9.7.FP1