| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IT08643 | Status: Closed |
DB2UNCOMPRESSLOG REPORTS CORRUPTED LOG FILE ERROR WHEN DECOMPRESSING A LOG FILE WITH MORE THAN 1 COMPRESSED BLOCK | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
When trying to decompress a compressed log file with the
external tool db2UncompressLog, the tool incorrectly reports
that the log file is corrupted. This problem only occurs when
the log file has more than 1 compressed block. Each compressed
block by default contains 32 pages of uncompressed log data.
Although the tool reports that the log file is corrupted, the
log file is actually valid.
Example Error Scenario
1. You have a compressed log file S0000000.LOG (generated with
enabling database configuration parameter LOGARCHCOMPR1/2)
2. You tried to decompress the log file using the
db2UncompressLog tool:
> db2UncompressLog -s0
DB2 LUW V10.1 -- Uncompress log files
Version 1.0
The given log file(s) will be uncompressed to file(s)
with the same log file name but with .EXP suffix,
if -inplace option is specified, the expanded log file
will be renamed to the original log file name.
Multiple Files Specified : FALSE
Start File Number : 0
End File Number : N/A
Replace the original compressed log files: FALSE
Quiet mode : FALSE
Processing file S0000000.LOG...
expanded block size is 131072
Log file S0000000.LOG corrupted offset 0x46cf7ee6
File S0000000.LOG done, 1 compressed blocks.
db2UncompressLog exit with return code 3.
3. You run the db2cklog tool on the log file and verified that
it is not corrupted.
> db2cklog 0
________________________________________________________________
____
_____ D B 2 C K L O G _____
DB2 Check Log File tool
I B M
The db2cklog tool is a utility can be used to test the
integrity
of an archive log file and to determine whether or not
the log file
can be used in the rollforward database
command.
________________________________________________________________
____
________________________________________________________________
________________
========================================================
"db2cklog": Processing log file header of "S0000000.LOG".
"db2cklog": Processing log pages of "S0000000.LOG" (total log
pages: "1000").
==> page "1" ...
"db2cklog": Finished processing log file "S0000000.LOG". Return
code: "0".
======================================================== | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users using db2 log compression. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Updrade to latest fix pack * **************************************************************** | |
| Local Fix: | |
There is no local fix, except move up to V105FP6 to get the fix or to use older versions of db2UncompressLog if the log file is not encrypted. | |
| Solution | |
Problem was first fixed in DB2 UDB Version 10.5 fix pack 7 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.04.2015 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 |
|
