|
Problem IT01377
|
Status: Closed |
THE DB2CKLOG TOOL MAY INCORRECTLY REPORT A LOG FILE AS INVALID |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When using the db2cklog tool to check the validity of a DB2
transaction log file, it may incorrectly report the current log
file is invalid.
For example:
"db2cklog": Processing log file header of "SXXXXXXX.LOG".
"db2cklog": Processing log pages of "SXXXXXXX.LOG" (total log
pages: "XX").
==> page "1" ...
DBT7072E Log file validation failed because the log record size
is invalid. Log record size: "485". The expected log record
size is "4076". The maximum valid log record size is
"18446744073709547812".
DBT7048E The db2cklog utility determined that the current log
file is invalid.
As shown in the above db2cklog output, if you see the maximum
valid log record size is having an extreme large value, like
"18446744073709547812", you may be hitting the APAR. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 5 or newer *
**************************************************************** |
| Local Fix: |
|
| Solution |
Problem was first fixed in Version 10.1 Fix Pack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.04.2014
13.07.2015
13.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
