Post reply

Flat file source working

  • September 7, 2009 at 4:01 am

    #156183

    Hi ,

    Would like to know flat file source works and how is metadata determined and the code page i am trying to flat file data into the table through dataflow task

    [Flat File Source [14276]] Error: Data conversion failed. The data conversion for column "Column 35" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".

    [Flat File Source [14276]] Error: The "output column "Column 35" (14434)" failed because truncation occurred, and the truncation row disposition on "output column "Column 35" (14434)" specifies f

    ailure on truncation. A truncation error occurred on the specified object of the specified component.

    How is this code page generated and determined ,Thanks for the help

    Thanks

  • September 7, 2009 at 5:25 am

    #1050052

    The code page is user configurable in the flat file connection manager.

    ---
    SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

  • September 9, 2009 at 5:35 pm

    #1051500

    Hi,

    Thanks for the reply, Can you please help in understanding on how the suitable code page can identified to set in the flat file source

    Thanks

  • September 9, 2009 at 5:43 pm

    #1051501

    forum member (9/9/2009)

    Hi,

    Thanks for the reply, Can you please help in understanding on how the suitable code page can identified to set in the flat file source

    Thanks

    But the setting is made in the connection manager and the flat file source is reading it from there. Why you keep repeating flat file source? Are you trying to change the code page at runtime in iteration?

    ---
    SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

  • September 10, 2009 at 4:55 am

    #1051652

    Is it that you are interpreting the error message as meaning that there is definitely a codepage problem?

    It is more likely that you are experiencing data truncation. What is the maximum length of column 35 in your source data? You might find it easier to work with your source data if you give the columns meaningful names.

    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

  • September 14, 2009 at 9:11 am

    #1053274

    Just curious - does column 35 happen to be the last column?

    I have seen cases where the line terminators were not defined correctly on the data source and the next line was considered part of the last column causing a truncation error.

    Otherwise - looks like the data in column 35 is bigger than your destination file is set to handle.

    Mike

    “I know that you believe you understand what you think I said, but I'm not sure you realize that what you heard is not what I meant.”...Robert McCloskey

    ___________________________________________________________________

  • September 14, 2009 at 12:11 pm

    #1053370

    mbricker (9/14/2009)

    --snip

    Otherwise - looks like the data in column 35 is bigger than your destination file is set to handle.

    Or that the pipeline meta-data column definition is too small.

    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

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply