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

CONCAT IN ORA MODE WITH NULL CLOB TYPES WILL RETURN NULL WHEN THE OTHER
VALUE IS NOT NULL

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The official document recorded that in ORA mode for CONCAT 
function and the concatenation operator, A null or empty string 
value is ignored in the concatenated result. 
http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com. 
ibm.db2.luw.apdv.porting.doc/doc/r0052880.html?lang=en 
This works fine for literals, but not for column values, the 
CONCAT will return NULL. Please see the following detailed test 
=> db2 "values cast('xyz' as clob(10))|| cast(null as clob(10))" 
1 
---------- 
xyz 
  1 record(s) selected. 
VS 
==> db2 "create table ken_clob(col1 integer,clob_col clob)" 
==> db2 "insert into ken_clob (col1) values (1)" 
==> db2 "insert into ken_clob values (2,'123')" 
==>db2 "SELECT CONCAT(clob_col, '123') FROM ken_clob" 
 
------------ 
-       <- The offender 
123123 
 
  2 record(s) selected.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Wrong results                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to latest v10.5fp7                                   * 
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.04.2015
19.01.2016
19.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList