home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC96602 Status: Closed

ARCHIVED LOG CORRUPTION POSSIBLE USING LOG COMPRESSION AND VENDOR SETTING

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When using log archived log compression ( enabled via 
LOGARCHCOMPR[1|2] ) 
in combination with a VENDOR library setting for the 
LOGARCHMETH[1|2] setting, 
the archived log may become corrupt if the Vendor library does 
not strictly implement the DB2 backup and restore API for Vendor 
products. 
 
This is the case with the Tivoli TDP library due to apar IC90724 
for which a fix 
needs to be requested
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to V10.5 Fix Pack 3 or higher.   * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
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
This problem was first fixed in V10.5 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.10.2013
27.02.2014
27.02.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList