|
Problem IT01055
|
Status: Closed |
ESTIMATED LOGFILESIZE PROVIDED BY DB2 TO TSM IS WRONG FOR TRUNCATED LOGFILES |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
During log archive, DB2 always provides the configured
logfilesize to TSM by default. The filesize for truncated
logfiles can differ heavily from the configured logfilesize.
Thus, the provided size of DB2 does not match the size of the
object very well. This APAR will fix the behavior of DB2 to
provide a better filesize for truncated logfiles as well. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 Fix Pack 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.5 Fix Pack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.04.2014
06.11.2014
06.11.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
