DB2 FOR LUW / DB2FORLUW / 970 - DB2

Upon making a log file retrieve attempt from TSM, db2 does not 
retry the retrieve if the retrieve failed, nor verify that the 
size of the log file retrieved is consistent with the expected 
size in the log file header.  This defect introduces logic to: 
verify the log files size matches the expected size; retry the 
retrieve exactly once if either the compared sizes do not match, 
or if there was an error retrieving the log file; inform the 
user via the diaglog that the retry was attempted and save the 
incorrect log file (if available) to the log file directory as 
well as issue diag warnings.  The second log file retrieved will 
also be saved if there is a size mismatch and diag log entries 
will be made.

DB2 retrieve log code improved to verify correct logsize as per 
log header and try second time again to retrieve the log from 
TSM if a mismatch occurs or an error is encountered retreiving 
the log file.

If the wrong sized tranaction log was previously retrieved and a 
correctly sized transaction log was archived successfully by 
TSM, use db2adutl to retrieve the correctly sized log.

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
 

Fixed in V97 FP5

If the wrong sized tranaction log was previously retrieved and a 
correctly sized transaction log was archived successfully by 
TSM, use db2adutl to retrieve the correctly sized log.

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

03.03.2011
22.12.2011
22.12.2011

9.7.FP5