March 10, 2006 at 2:34 pm
Currently we have jobs running using DTS that transform data from an Oracle db to a SQL server db. I have attempted to re-create these jobs in SSIS however the non-implicit conversion seems to be too non-implicit.
All data types are defined as nvarchar2 in Oracle and exist in a sql server typed as nvarchar. Since these are both unicode types, why is this provider reading it as non unicode?
I did find that the .net oracle provider fixed the unicode/non unicode error however the size of the source field is 1.5 times in the destination. The package will run but I get truncation warnings throughout execution.
Any feedback on these is greatly appreciated!
Thanks,
Barbara
March 10, 2006 at 5:13 pm
I saw this, btw: http://forums.oracle.com/forums/thread.jspa?threadID=226114&tstart=30
Also, maybe the .net provider can't figure out whether your nvarchar(2) source data is UTF-8 or UTF-16. I don't know if SQL Server can handle UTF-8?
October 20, 2006 at 6:57 am
Check out the DataType settings in the advanced editor. I had several occasions where the data type of the external columns and the output columns did not match. After setting the data type manually everything worked fine for me. I am still wondering if this is a bug or a feature...
Regards,
Rainer
October 20, 2006 at 7:39 am
We actually tracked down the solution to this, you have to have the latest & greatest Oracle OLEDB driver. Anything less & you get errors either in the size of the field or in the data types.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply