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

SUBSTRB MAY RETURN WRONG RESULT WHEN START OR LENGTH VALUE IS NULL

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The SUBSTRB built-in function may return an empty string intead 
of the expected null result when the start value (second 
argument) 
or length value (third argument) is null, e.g.: 
 
create table a (c1 int) 
DB20000I  The SQL command completed successfully. 
 
insert into a values(NULL) 
DB20000I  The SQL command completed successfully. 
 
select substrb('hello',c1) from a 
 
1 
----- 
     <= should be null, empty string instead 
 
  1 record(s) selected.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 fix pack 4                       * 
****************************************************************
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
First fixed in DB2 version 10.5 fix pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.12.2013
08.09.2014
08.09.2014
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