January 4, 2011 at 3:59 am
What are the exact errors that you get?
Maybe you can give the schema definitions of the source table and the destination table, and if possible, some sample data. Also explain what you are trying to accomplish. That way it's easier for us to help you.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 4, 2011 at 4:29 am
Hi,
The error i see in the data flow task before executing the package. Currently we are using that package for data extraction from Oracle source and we were not using any unicode conversions. Now, based on requirements we need to load one column A data with unicode and that column has unicode characters at source as well. Hence i have modifed the destination column to handle (nvarchar) data type. I have used data coversion in SSIS to load as unicode (its given as Unicode [DT-WSTR]) and destination is also mapped with that coversion label and there is no issues with that column. But the issue is at destination table where i see Red icon and all other columns which are in that table are showing as "Column X could not convert between Unicode and non-unicode characters". I don't want to covert all other columns to unicode format, i want to keep them as is and they have few columns as int and few as varchar. I even refreshed the mappings but no luck.
January 4, 2011 at 4:53 am
How come you are getting errors on columns X, when you are supposed to load only one column?
Did you select all columns at the source?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 4, 2011 at 6:54 am
Hi,
I am selecting around 30 columns from source with respective column names, out of which i am converting only one column as Unicode character. Rest other columns i need them as is with their current data types. The package works fine when i don't do any unicode conversions. However, when i do conversion for that one column it starts showing errors for all other columns except for the one that has converted.
January 4, 2011 at 6:57 am
That's weird. You can check the advanced editor of the source component to see which datatypes SSIS uses for the other columns. If they are unicode, change them back to non-unicode.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 4, 2011 at 8:27 am
In advanced editor of source component, i just changed columns datatype to String DT-STR for both External and Output columns which was showing as Unicode earlier. After that change i remapped the source and destination but still same error. when i checked the external and output columns again, it was showing as Unicode again. I am using Native OLEDB/Oracle Provider for OLEDB for source connection.
January 4, 2011 at 11:00 am
Hmmmm. Maybe you can convert the rest of those columns to DT_STR and use varchar in the destination.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 4, 2011 at 12:07 pm
When I have a problem like this I find it easiest to go directly to the code/xml and edit there.
In BIDS, with your package loaded in the design window go to View >> Code. Then search for the column name that is giving you trouble and edit the data definitions directly there. You will probably find at least 1 that is out of sync with the others. Then save it and close it and you should be good to go.
Viewing 8 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply