DB2 FOR LUW / DB2FORLUW / A10 - DB2

When we insert "NULL", which is the output of a UDF,   into a 
column of a nickname that does not allow NULL values, you may 
not receive a SQL0407N error as expected, but actaully the 
insert operation is actaully failed, 0 rows is inserted. 
 
The issue is easy to recreate: 
 
SET PASSTHRU SQLSERVER 
CREATE TABLE [dbo].[t2]([c1_notnull] [datetime] NOT 
NULL,[c2_null] [datetime] NULL) 
SET PASSTHRU RESET 
 
CREATE NICKNAME T2 FOR SQLSERVER.dbo.t2 
 
CREATE OR REPLACE FUNCTION STRINGTODATE 
( 
   STR VARCHAR(23) 
) 
RETURNS DATE 
SPECIFIC STRINGTODATE 
LANGUAGE SQL 
DETERMINISTIC 
NO EXTERNAL ACTION 
CONTAINS SQL 
BEGIN 
   DECLARE rdate  DATE; 
   --DECLARE CONTINUE HANDLER FOR SQLEXCEPTION SET rdate = null; 
   SET rdate = DATE(STR); 
   RETURN rdate; 
END 
 
db2 => INSERT INTO T2(c1_notnull,c2_null) SELECT 
STRINGTODATE(NULL),DATE('2012-06-25 15:00:00.000') FROM 
SYSIBM.SYSDUMMY1 
DB20000I  The SQL command completed successfully. 
 
NOTE: It said insert successfully but actually failed!

**************************************************************** 
* USERS AFFECTED:                                              * 
* The users are inserting "NULL", which is the output of a     * 
* UDF,   into a column of a nickname that does not allow NULL  * 
* values.                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to InfoSphere Federation Server v101fp2 or later.    * 
****************************************************************

DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

The problem is first fixed at v101fp2.

not known / see Local fix

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

17.11.2012
31.12.2012
31.12.2012