Post reply

UNICODE problem using Attunity 2.0 connection to Teradata

  • December 2, 2013 at 1:12 am

    #283046

    Hi,

    I'm trying to connect in SSIS to a Teradata 14.00 to get data via the Attunity driver 2.0. (using TPT 14.10) It's working well and the performance is amazing. But there's a problem for me:

    The VIEW that I'm querying is defined returning the string with CHARSET ASCII (default in our Teradata). In the destination the strings should be in UNICODE format. I thought the parameter UseUTF8Charset (default setting is true) in Teradata Connector would handle this for me?! But if I check the metadata of my source the datatype is DT_STR. That's why the connection to the target fails with "cannot convert between unicode and non-unicode".

    Does anyone has an idea how to handle this? Using the .NET provider everything went fine with the CHARSET ...:crazy:

    Thanks in advance

    Helmut

  • December 2, 2013 at 2:21 am

    #1670030

    Hi,

    Please try to change data type to Unicode string [DT_WSTR]

    in source connection.

    Br.

    Mike

  • December 2, 2013 at 4:32 am

    #1670063

    Hi Mike,

    I tried this already (using "Show Advanced Editor" of Source --> "Input and Output Properties" --> "Output"), but after closing the dialog box and saving the package the re-open of the Advanced Editor showed again dt_str instead of dt_wstr.

    Could this be done anyhow else?

    Thanks in advance

    Helmut

  • December 2, 2013 at 5:20 am

    #1670076

    Maybe this helps:

    In the log File of TPT I can see that the session character set on Teradata is UTF8. Seems to work fine in this place.

    As far as I know Attunity Teradata Source/Destination gets the metadata of Teradata via ODBC... Does the setting of the UseUTF8CharacterSet=true also affect the ODBC part?

    Best regards

    Helmut

  • December 2, 2013 at 6:45 am

    #1670100

    Please add Data Conversion Task between Source and Destination.

    Br.

    Mike

  • December 2, 2013 at 6:57 am

    #1670106

    Hi Mike,

    thanks, but if this is the only way to do that, I have to de-install the Attunity stuff.

    This would cause me to change about 50 packages where I have to add the conversion of altogether maybe 1000 columns!

    In my opinion the SESSION CHARACTER SET UTF8 on Teradata side should do exactly what I want, return all string columns to UNICODE. (otherwise, what is the meaning of setting UseUTF8CharacterSet = true?)

    Best regards

    Helmut

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

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