DB2 FOR LUW / DB2FORLUW / A50 - DB2

When trailing blanks are truncated from a LOB value during 
storage assignment, the statement execution should fail with 
SQL0433N.  However, under some circumstances, the blanks will be 
truncated without warning or error.  This can happen with the 
source string is a LOB data type and the target is non-LOB.  For 
example: 
 
  create table T1 ( C1 char(5) for bit data ); 
  DB20000I  The SQL command completed successfully. 
 
  insert into T1  values blob('12345   '); 
  DB20000I  The SQL command completed successfully. 
 
Similarly, when the target is a LOB and the source is not a LOB, 
a SQL0433N error may occur on blank truncation, there should be 
no error or warning in this case.  For example: 
 
  create table T2 ( C1 dbclob(5) ); 
  DB20000I  The SQL command completed successfully. 
 
  insert into T2 values char('12345     '); 
  SQL0433N  Value "12345     " is too long.  SQLSTATE=22001

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* If space truncation from LOBs is undesirable, write          * 
* application to avoid it                                      * 
****************************************************************

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
 

not known / see Local fix

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

13.06.2014
15.09.2014
15.09.2014