17.20 - Supported Client Character Sets - Analytics Database - Teradata Vantage

Teradata Vantageā„¢ - Analytics Database International Character Set Support - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-01-27
dita:mapPath
aju1628095815656.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
hqj1472245413611

The KANJI1 server character set is designed to support Japanese characters only when using specifically designed client character sets.

KANJI1 supports single-byte characters from the following client character sets:

  • EBCDIC
  • ASCII
  • UTF8

    Only single-byte characters that are coded the same in the LATIN and JIS X 0201 standard can be used.

KANJI1 supports mixed single- and multibyte characters from the following client character sets:

  • KanjiEBCDIC
    • Single-byte data uses JIS X 0201
    • Double-byte data uses SO/SI
  • KanjiSJIS_0S
    • JIS X 0201
    • JIS X 0208
  • Kanji1932_1S0
    • JIS X 0201
    • JIS X 0208
  • KanjiEUC_0U
    • JIS X 0201

      Bytes 00-7F as defined

      Byte 8E mapped to 80

    • JIS X 0208 (converted to KanjiSJIS)
    • JIS X 0212

      Byte 8F mapped to FF

Only a limited set of characters stored as KANJI1 can be retrieved correctly by a client character set other than the one that entered the data. This limited set includes most 7-bit ASCII characters:

  • The letters A-Z and a-z
  • The digits 0-9
  • Various punctuation, symbols, and control characters

In general, it does not include:

  • Japanese characters
  • The backslash (\)
  • Yen sign
  • Tilde
  • Overline

Attempts to retrieve Japanese or other non-sharable characters from a KANJI1 field may result in error messages for the following character sets:

  • UTF8
  • UTF16
  • Most site-defined client character sets using map files

For other character sets, attempts to retrieve Japanese or other non-sharable characters from a KANJI1 field may result in improperly translated data.