Post reply

SSIS - Oracle Source character set changed from non unicode to Unicode - Do I need to change the code?

  • September 10, 2012 at 1:06 pm

    #266457

    Hi,

    Our source database Oracle is changed from non Unicode to Unicode. The mappings were done with source DT_STR for source and target external columns.

    Do I need to change the code to DT_WSTR for source and Target external columns with unicode conversion transformation?

    Or changing the Target SQL Server database character set will resolve the issue?

    Thank You.

  • July 4, 2013 at 4:19 am

    #1629795

    I know this is an old thread, but I came across a quickfix for this. Our Oracle drivers failed and we had to reinstall newer ones and all of our 64 bit SSIS Packages failed as the non-unicode fields in Oracle were presented as unicode invalidating all of the ETL Packages.

    It was a slightly worrying thought that we may have to edit each individual package. But on the Oracle forums we came across this link

    https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?returnToSrId=&srnum=&_afrLoop=101583591816790&type=DOCUMENT&id=960508.1&displayIndex=2&_afrWindowMode=0&_adf.ctrl-state=543vx1hd2_87

    You'll need an Oracle account to see it. Essentially we had to add an NLS_LANG setting with the correct setting to change the metadata reported by the OLEDB Provider. In our case another box with the older driver had a setting of ENGLISH_UNITED KINGDOM.WE8MSWIN1252 in the NLS_LANG. Adding this registry entry in the Oracle Home area for the 32 bit and 64 bit drivers fixed the issue immediately.

    Not a big fan of reg hacks but I hope this helps anyone that is searching for this and hasn't come across a quick fix. 🙂

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply