We need to store and export data from Teradata having Chinese characters.The data will be exported by an export utility like FastExport/TPT.For testing purpose I created the table in SQL assistant as shown below:
INSERT INTO charsettest VALUES(1,'李白《静夜思》');
The data got inserted successfully.I made the install flag as Y in DBC.charTranslationsV as Y for the below Client character sets:
Now coming to the problems I am facing currently:
Is there anything I am missing here?Also is it possible to export a chinese character set in FastExport or TPT?
This CLI error "*** CLI error: MTDP: EM_CHARNAME(227): invalid character set name specified. *** Return code from CLI is: 227" is typically returned when the character set is not installed properly. Did you
perform a full restart of the Teradata Database, using the tpareset utility? If so, check the system event log for any 2900 errors during the restart for installing character sets.
The problem is resolved by setting the session character set of the ODBC driver to UTF8.
Also data is exported properly(including all the Chinese characters) using FastExport by using "UTF8" character set using -c option while invokation of the FastExport command.
Yes, UTF8 is in wide use on the web. It is also a better choice because the TD16 Unicode Pass Through (UPT) feature will allow any Chinese character to be loaded as a pass through, or supported, character. This is even true for the soon to be released Unicode version 10.0. Note that the stand-alone fastexport utility does not currently support UPT, use TPT instead.
The following Chinese character sets will only support the 2-byte ideographs from the 6.0 BMP:
I was wondering why we need separate Chinese client character set(Ex:SCHINESE9360_6R0)
as given below if we are able to support all chinese Characters by using "UTF8" itself?
Can you please mention a use case where we need this Chinese Character set and UTF8 won't solve the purpose?
It depends on the Windows code page in use. SCHINESE9360_6R0 is used for code page 936. If the windows platform supports UTF8 (which all should today), then use it.