Post reply

DATA conversion error

  • December 9, 2010 at 1:32 am

    #146540

    HI all,

    I am trying to import the records from DB2 source to SQL server destination.

    Source column datatype: varchar(1000)

    Target column datatype: varchar(1000)

    I am using the dataconversion task to convert the "unicode staring 1000" to "string 1000". since oledb destination does not accept unicode string. I am getting the below error when executing the package:

    error message:[Data Conversion [1878]] Error: Data conversion failed while converting column "CMNT_T_SRC" (2759) to column "CMNT_T_SRC" (2833). The conversion returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".

    Source column data looks like the below:

    "confirmed cost $3.85/lbs &1.59/yd @60"cw FOB $1.72@65 cw (Before washed 130g/m2) washing0.08+workingloss0.07+iff0.13 =CIF$ 2.00 Artwork#201/202/205 Print upcharge avg d out - $ 0.45/yd ( print $0.41/yd for each + add l f.wash prior to print $0.12/yd for artwork#202) Case 2) When the print upcharge is not avg d out. Artwork#202 print upcharge $0.53/yd (print $0.41/yd + add l f.wash prior to print $0.12/yd)"

    Please help me on this. thanks in advance.

  • December 9, 2010 at 1:42 am

    #1260454

    marees.inspire (12/9/2010)

    I am using the dataconversion task to convert the "unicode staring 1000" to "string 1000". since oledb destination does not accept unicode string.

    nVARCHAR for Unicode. You mention going to SQL Server, it definately accepts unicode.

    I am getting the below error when executing the package:

    error message:[Data Conversion [1878]] Error: Data conversion failed while converting column "CMNT_T_SRC" (2759) to column "CMNT_T_SRC" (2833). The conversion returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".

    The data is 419 characters, so my guess is there's a character in there that doesn't match whatever code page it thinks it's supposed to get, especially in non-unicode. Try shipping it to an nVARCHAR field, see what happens.

    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
    Twitter: @AnyWayDBA

Viewing 2 posts - 1 through 1 (of 1 total)

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