April 11, 2014 at 7:52 am
Ok, I've been confronted by this problem during the week where I'm the only guy not on break on our SQL team.
I got a series of databases that have data concerning clients in Asia,now this week (about 3 months after go live) we get the report the Chinese characters have turned into ?
The source is an IBM DB2 UDB for iSeries IBMDASQL OLE DB Provider,in the preview the characters are shown correctly but they turn into ? as soon as they leave the source.
The fields are string [DT_STR] codepage 1252,here lies the problem,this causes the Chinese characters to be turned into ?.
However when I change it to unicode type,the package errors on the source. Is their any solution for this.
April 11, 2014 at 8:19 am
Resender (4/11/2014)
Ok, I've been confronted by this problem during the week where I'm the only guy not on break on our SQL team.I got a series of databases that have data concerning clients in Asia,now this week (about 3 months after go live) we get the report the Chinese characters have turned into ?
The source is an IBM DB2 UDB for iSeries IBMDASQL OLE DB Provider,in the preview the characters are shown correctly but they turn into ? as soon as they leave the source.
The fields are string [DT_STR] codepage 1252,here lies the problem,this causes the Chinese characters to be turned into ?.
However when I change it to unicode type,the package errors on the source. Is their any solution for this.
What exactly are you changing when you 'change to Unicode type'?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
April 11, 2014 at 8:29 am
Phil Parkin (4/11/2014)
What exactly are you changing when you 'change to Unicode type'?
I go into the advanced editor and change the datatype of the column
April 11, 2014 at 8:52 am
Resender (4/11/2014)
Phil Parkin (4/11/2014)
What exactly are you changing when you 'change to Unicode type'?I go into the advanced editor and change the datatype of the column
Can you post the error message?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
April 11, 2014 at 9:00 am
When trying to execute with the colums put on unicode, via advanced editor
TITLE: Package Validation Error
------------------------------
Package Validation Error
------------------------------
ADDITIONAL INFORMATION:
Error at Pull [Source [1]]: The output column "VNDNAM" (1294) on the error output has properties that do not match the properties of its corresponding data source column.
Error at Pull [SSIS.Pipeline]: "component "Source" (1)" failed validation and returned validation status "VS_NEEDSNEWMETADATA".
Error at Pull [SSIS.Pipeline]: One or more component failed validation.
Error at Pull: There were errors during task validation.
(Microsoft.DataTransformationServices.VsIntegration)
------------------------------
BUTTONS:
OK
------------------------------
------------------------------------------------------------------------------------------------------
TITLE: Editing Component
------------------------------
The component is not in a valid state. The validation errors are:
Error at Pull [Source [1]]: The output column "VNDNAM" (1294) on the error output has properties that do not match the properties of its corresponding data source column.
Do you want the component to fix these errors automatically?
------------------------------
BUTTONS:
&Yes
&No
Cancel
------------------------------
April 13, 2014 at 1:36 pm
Did you modify the datatype of the column in both 'External Columns' and 'Output Columns'?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
April 14, 2014 at 1:41 am
Phil Parkin (4/13/2014)
Did you modify the datatype of the column in both 'External Columns' and 'Output Columns'?
yes I changed them both from string DT_STR to DT_WSTR & that leads to the aforementioned error message
April 14, 2014 at 3:00 am
Resender (4/14/2014)
Phil Parkin (4/13/2014)
Did you modify the datatype of the column in both 'External Columns' and 'Output Columns'?yes I changed them both from string DT_STR to DT_WSTR & that leads to the aforementioned error message
And are you directing errors somewhere else? Have you also checked the error output?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
April 14, 2014 at 5:03 am
There no error message except for the validation error,cause that stops the execution of the rest of the package
April 14, 2014 at 5:11 am
Resender (4/14/2014)
There no error message except for the validation error,cause that stops the execution of the rest of the package
I mean are you redirecting error rows - have you checked the error output?
Like this, I mean.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
April 14, 2014 at 5:24 am
Phil Parkin (4/14/2014)
Resender (4/14/2014)
There no error message except for the validation error,cause that stops the execution of the rest of the packageI mean are you redirecting error rows - have you checked the error output?
Like this, I mean.
I know what you meant,I tried that, the problem is that if I use the unicode datatype in the source I'm getting no execution what so ever.
I get the build Succeeded - Package Validation Error - Package Stops executing
With the strings and error redirect no rows error but their all the chines characters turn into ?
If that's what you meant
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply