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 IT03076 Status: Closed

DATA CORRUPTION POSSIBLE AFTER RECREATING PAGE DICTIONARY

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
For a table with adaptive compression active, corruption may be 
introduced on the page if the page level dictionary is 
recreated. This will result in the loss of a row when two rows 
share the same offset into the page. In addition, the free space 
on the page will be incorrect and you might also see index 
corruption symptoms. 
 
The problem can be detected by both db2dart and inspect. 
 
After applying the fix, a roll forward through an affected page 
dictionary recreation log record will fail.  If this happens, 
call DB2 Support for assistance.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of adaptive compression                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the latest fix pack.                              * 
****************************************************************
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
Problem is first fixed in DB2 UDB version 10.5 fix pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.07.2014
08.09.2014
09.04.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList