Dear Microsoft-Team,
I have a really weird problem with the varchar values. I will explain it to you. I have started the cdc service to catch the updated data. But the source data are really different when I get them to my SQL Server 2012 Instance…
See 2 examples:
Source Type, Source Value, Destination Type , Destination Value
Varchar2, '164f3293-e5fa-435e-a15d-f67ab12b1486', nvarchar, ‘ㄶ㑦㌲㤳ⵥ㕦愭㐳㕥ⵡㄵ搭昶㝡戱㉢ㄴ㠶’
Varchar2, '164f3293-e5fa-435e-a15d-f67ab12b1486', varchar, ‘??????????????????’
I have on the SQL Server Instance the Latin_General_CI_AI Collation and I have tried 5-6 more but that is not really important for the sql server. The numeric values work fine and when using an SSIS I get the right data to the destination tables.
The CDC services read probably the Data from the Archive Log so there must be the problem. I have already checked it with the SQL Profiler but I couldn’t see anything weird. I have run this query on the oracle database:
select parameter,value from v$nls_parameters.
Weird Parameters for me :
NLS_NCHAR_CHARACTERSET, NLS_LENGTH_SEMANTICS
I have tried a lot of things before I decided to write you… Thanks for any help.
The Results:
Oracle Database:
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY <st1:country-region w:st="on"><st1:place w:st="on">AMERICA</st1:place></st1:country-region>
NLS_CURRENCY $
NLS_ISO_CURRENCY <st1:country-region w:st="on"><st1:place w:st="on">AMERICA</st1:place></st1:country-region>
NLS_NUMERIC_CHARACTERS .,
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_CHARACTERSET AL32UTF8
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
Regards,
Rena