KANJI1 Character Expectations - Advanced SQL Engine - Teradata Database

International Character Set Support

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-23
dita:mapPath
ywb1588027283948.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1125
lifecycle
previous
Product Category
Teradata Vantage™

KANJI1 character data is usually a mixture of single- and multibyte characters. Therefore, even when a session uses a non-Japanese client character set, such as standard EBCDIC or ASCII, certain character configurations are interpreted either as starting a multibyte character string or as control characters.

The following interpretations apply to name and data characters for all client character sets when the server character set is KANJI1.

Characters with a client encoding of … Are …
0x0E

0x0F

interpreted as the Shift-Out or Shift-In character respectively, which delimit the start or end of a multibyte character string.
0x80

0xFF

translated internally into characters that are reserved for the ss 2 and ss 3 escape characters of KanjiEUC data.