In accordance with Teradata internationalization plans, KANJI1 support is deprecated and is to be discontinued in the near future. KANJI1 is not allowed as a default character set; the system changes the KANJI1 default character set to the UNICODE character set. Creation of new KANJI1 objects is highly restricted. Although many KANJI1 queries and applications may continue to operate, sites using KANJI1 should convert to another character set as soon as possible. For more information, see KANJI1 Character Set in Teradata Vantage™ NewSQL Engine International Character Set Support, B035-1125.
Character string functions do not work on all characters in the KANJI1 server character set when the session character set is UTF8 or UTF16, because the KANJI1 server character set is ambiguous in regard to multibyte characters and some single-byte characters.
Recommendation: Unless the KANJI1 server character set is required, use the UNICODE server character set with the UTF8 and UTF16 session character sets for best results.
The following single-byte characters in KanjiEBCDIC to KANJI1 translations are mapped to the following Unicode character names.
|Hexadecimal Value||Character||Unicode Character Name|
However, with a KanjiSJIS character set, these hexadecimal values map to control characters.