I had a weird error today. I had an Oracle source table, and a SQL Server Destination table, and got an error in the dataflow component for the OLE Destination. The error was for both columns for the table and was "Column [the column name] cannot convert between unicode and non-unicode string data types". All other tables in my data flow were converting just fine, so it was really a mystery.
This is the fix: in the OLE DB destination - right click and go to the Advanced Editor, go to the Input and Output Properties, click the Destination Input/External Columns. Each of the columns' data type was set to Unicode string [DT_WSTR] - I changed it to string[DT_STR], which is what the the other columns were set to. The "red x" on my destination immediately went away, and my package executed just fine!
I don't know what it was about that particular table that caused the problem...
Tuesday, May 18, 2010
SSIS DefaultCodePage Warning
I found this on an EMC Consulting blog - it fixed my warnings -
I've been trying to access data in Oracle from SSIS via OLE DB and was getting the following warning:
"Cannot retrieve the column code page info from the OLE DB Provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used."
The fix is simple. Set AlwaysUseDefaultCodePage=TRUE on the offending OLE DB Source component and it works fine.
I've been trying to access data in Oracle from SSIS via OLE DB and was getting the following warning:
"Cannot retrieve the column code page info from the OLE DB Provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used."
The fix is simple. Set AlwaysUseDefaultCodePage=TRUE on the offending OLE DB Source component and it works fine.
Subscribe to:
Posts (Atom)