|
Problem IT05914
|
Status: Closed |
DB2CKLOG MIGHT WRONGLY REPORT A LOGFILE AS INVALID, IF IT IS A TRUNCATED LOGFILE |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
db2cklog might report the following for a log file that was
truncated by eg ARCHIVE LOG command.
========================================================
"db2cklog": Processing log file header of "S00nnnnn.LOG".
"db2cklog": Processing log pages of "S00nnnnn.LOG" (total log
pages: "6843").
==> page "1" ...
==> page "1001" ...
==> page "2001" ...
==> page "3001" ...
==> page "4001" ...
==> page "5001" ...
==> page "6001" ...
DBT7067E Log file validation failed because a log page ends
with an unexpected log record type. Header flag of the log
page: "0x001C". Unexpected log record type: "0x0084".
DBT7048E The db2cklog utility determined that the current log
file is invalid.
"db2cklog": Finished processing log file "S00nnnnn.LOG". Return
code: "0".
======================================================== |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.5 fixpack 7 *
**************************************************************** |
| Local Fix: |
n/a |
| Solution |
Problem was first fixed in DB2 version 10.5 fixpack 7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.12.2014
22.01.2016
22.01.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
