0 - 9 of 9 tags for utf8



I need to export few chinese and japanese characters stored in teradata to a file.


I have tried different options to export data through TPT but i am either not able to see the unicode characters in the generated file or i face the conflicting data length error.


I am using charset as UTF8 in fastlload, whatever record has special character like box went to Error table (ET). Pls refer the attachment for the sample issued value. Kindly help me how to handle this situation, we need to load data as it is there in source.

Teradata 13.10 is rejecting my insert with the error:
 The string contains an untranslatable character. (6706)
Here is my INSERT statement:
Insert Into CCDW_T.UTest (ucol, i) SELECT 'ɂ',578;
This is my CREATE Table:

Hi ,
   I am facing problem when i upload  files exported using bteq into MYSQL
the problem mysql reads NULL as 'NULL ' so falls over
any help on this would be great.
Thank you


UDF : utf8to16 function:
why is it known as Latin to Unicode conversion function when utf8 and 16 both represent unicode encoding?

my question is about the output of a UNICODE column in BTEQ.

If I select a column defined like this...
.. it is not 11 characters wide , but it is 33 characters wide
(3 times the number of VARCHARs)

The bteq session character set is UTF8: .set session charset 'UTF8';

The Unicode™ standard defines five encodings (the first three encodings are currently supported by Teradata):

Teradata 13.10 provides Algorithmic Compression (ALC) feature that allows  users to apply compression / decompression functions on a specific column of character or byte type. The compression / decompression functions may be Teradata built-in functions provided along with ALC or user provided compression / decompression algorithm registered as UDFs.

Workstation BTEQ recently added Unicode Support to its list of capabilities.  This article will explain to you how to start a Unicode BTEQ session in both interactive and batch mode. Command line options have been provided to give you control and flexibility to execute BTEQ in various Unicode environments, while preserving BTEQ’s legacy behavior.