DB2 FOR LUW / DB2FORLUW / A10 - DB2

Oracle wrapper removes trailing blanks at the end of a varchar 
host variable in insert/update statement. 
The problem only happens if remote Oracle table has varchar 
columns defined with char semantic. 
 
We can recreate the issue with following scripts: 
 
bad.sql 
~~~~~~~~~~~ 
drop server testserv@ 
create server testserv type oracle version 11 wrapper net8 
options(node 'oracl',VARCHAR_NO_TRAILING_BLANKS 'Y')@ 
create user mapping for db2inst1 server testserv 
options(remote_authid 'scott',remote_password 'tiger')@ 
 
set passthru testserv@ 
drop table test@ 
create table test( c1 VARCHAR2(20 CHAR))@  <== char semantic 
set passthru reset@ 
 
create nickname testn for testserv.scott.test@ 
drop PROCEDURE testp@ 
CREATE PROCEDURE testp () 
     SPECIFIC testp 
     LANGUAGE SQL 
   BEGIN 
     DECLARE v1 varchar(20) ; 
     set v1 = '123  '; 
     insert into testn values(v1); 
   END @ 
 
insert into testn values('123  ')@ 
call testp()@ 
 
select hex(c1) from testn@ 
 
db2 -td@ -f bad.sql 
 
DB20000I  The SQL command completed successfully. 
 
 
  Return Status = 0 
 
 
1 
---------------------------------------- 
3132332020 
313233 ==> blanks at the end are removed. 
 
  2 record(s) selected. 
 
A server option DB2_RTRIM_FOR_CHAR_SEM_COL will be added with 
'Y' as default. By default, it will work as before, column will 
be rtrimed in some cases as above. If DB2_RTRIM_FOR_CHAR_SEM_COL 
was set to 'N', no columns would be rtrimed. 
 
 
LOCAL FIX: 
 
Create remote Oracle table without char semantic, then recreate 
the nickname.

User affected: 
  Users who use Oracle wrapper of  in InfoSphere Federation 
Server 
Problem description and summay: 
  See error description

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
 

Problem was fistly fixed in Version 10, FixPak 2. This 
fix should be applied on the federation Server.

not known / see Local fix

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

28.11.2012
04.01.2013
04.01.2013