You mentioned the SQl Server table stores the data in nvarchar/nchar. It seems you're hitting an issue with the gateway which adds an additional space to every character replicating nvarchar data in PL/SQL code (defect 13950747 - NCHAR/NVARCHAR USING DG4MSQL ADDS A SPACE/BLANK TO EVERY CHARACTER USING PL/SQL ). It is currently being worked on this issue.
Edited by: kgronau on Dec 21, 2012 6:50 AM
Which gateway are you using and could you please provide the gateway init file and just in case you're using DG4ODBC also please upload the odbc.ini file.
kgronau wrote:Oh no, thats the odbc.ini on the windows machine where the HS listener is running from. My Oracle database is on Solaris.
So you're using Windows - what's the character set of your Oracle database (select * from v$nls_parameters)?
kgronau wrote:Hi Klaus,
I see ...
There are a few know work arounds like for example it worked for some customers when using a Unicode Oracle database.
Could you please try to change the insert statement using a full qualified object name like which also includes the username:
insert into tmp_cparties select "lngCounterpartiesUniqueID","strCounterpartyName" FROM "dbo"." tblcounterparties"@NEDSQL;
Does that work for you?