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

Log Replay of Update LOB Field Concatenation Can Cause Corruption

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
If a LOB field has been appended with an update command (e.g. 
using the || operator or the CONCAT scalar operator), it may 
become corrupted if either of the following scenarios occur: 
 
1. If a LOB is appended after a backup is taken, restoring from 
the backup and rolling forward such that the concatenation is 
replayed can corrupt the LOB. 
2. In HADR scenarios, a LOB concatenation operation on the 
primary can be incorrectly replayed on the secondary, corrupting 
the LOB. 
 
In both cases, the target LOB to be updated must contain the 
original version of itself as one of the concatenation 
arguments. The concatenation of other values written to the 
target LOB will not result in corruption. 
 
If corruption did occur, the LOB will appear to be truncated. 
Although the length as indicated by LENGTH(column) will report 
the non-corrupted size of the concatenated LOB, the actual LOB 
will appear to be shorter than what it should be.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* An error in LOB concatenation in log replay can cause the    * 
* LOB to be concatenated to overwrite portions of the previous * 
* LOB.                                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.5 Fix Pack 8.                              * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This problem was first fixed in DB2 V9.5 Fix Pack 8.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.03.2011
24.06.2011
24.06.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList