Used "Data Conversion" Transformation - VS_ISBROKEN - cannot convert between unicode and non-unicode string data types.
Friday, September 14, 2012 11:35 PM
Our Oracle source changed from Non-Unicode to Unicode. So I am using "Data Conversion" Transformation to convert the DT_WSTR to DT_STR to match the target SQL Server sting/text.
I am getting following error.Error at Load Audit_Log [ViewPoint AUDIT_LOG Source ]: Column "Column1" cannot convert between unicode and non-unicode string data types.
Error at Load Audit_Log [ViewPoint Table Source ]: Column "Column2" cannot convert between unicode and non-unicode string data types.
Error at Load Table [SSIS.Pipeline]: "component "DB Table Source" (1)" failed validation and returned validation status "VS_ISBROKEN".
Error at Load Table [SSIS.Pipeline]: One or more component failed validation.
Error at Load Table : There were errors during task validation.
We are not planning to change the Target table structure, so using the Data Conversion function to change it to Non-Unicode.
Really appreciate your thoughts.
- Edited by chalams Friday, September 14, 2012 11:36 PM
Saturday, September 15, 2012 7:39 AM
Check the links below. It may help you.
Saturday, September 15, 2012 6:28 PMYou can either choose to type cast the data in the oracle source db query or you can use a data conversion transformation.
Sunday, September 16, 2012 2:29 AMModerator
If you already had your SSIS package designed, then the Oracle Source changed data types, then the SSIS Source may not have caught that change.
I would try deleting the SSIS Source you're using and drop a new one on the surface. Configure it as you had before, and it should output Unicode types. Then use a Data Conversion transformation if you need to.
Talk to me now on
Monday, September 17, 2012 4:33 PM
Source identified as DT_WSTR for both output and external columns when I loaded the package with new database connection which is Unicode. Do I still need to drop and re import the source? No Errors shown at source or target in the Data Flow. But it throws error while debugging.
I am a newbie. Thank You.
Monday, September 17, 2012 4:34 PM
Thank You Patrice. But it does not help much.
I did the same data conversion in a sample package. It works fine.
Monday, September 17, 2012 4:46 PMModerator
If removing and then adding the source back does not help, then consider revising the Code Page setting.
I just found you a valuable thread to skim thru: http://social.msdn.microsoft.com/forums/en-US/sqlintegrationservices/thread/dc1a61f2-1ab8-4ed3-b85c-db6481800b50/
Pay attention to someone saying:
... set the OLE DB Source to AlwaysUseDefaultCodePage to True. The DefaultCodePage should be set to 1252 which is correct for Western Alphabet. If Oracle is not using the Western Alphabet, you'll need to determine the charset used and use http://msdn.microsoft.com/library/default.asp?url=/workshop/database/tdc/reference/CharSet.asp to correctly set the default code page.
Arthur My Blog