DB2 FOR LUW / DB2FORLUW / 910 - DB2

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.

**************************************************************** 
* 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.1 Fix Pack 11.                             * 
****************************************************************

N/A

DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows
 

This problem was first fixed in DB2 V9.1 Fix Pack 11.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC75322 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

28.03.2011
16.11.2011
16.11.2011

9.1.FP11