|
Problem IC74765
|
Status: Closed |
DB2 retrieve log code improved to verify correct logsize as per header and try second time to retrieve the log from TSM. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
DB2 retrieve log code improved to verify correct logsize as per
header and try second time to retrieve the log from TSM. |
| Local Fix: |
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. |
| available fix packs: |
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
|
| Solution |
Fixed in V95 FP8 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC74766
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.03.2011
15.07.2011
15.07.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
