Teradata Support for Common Client Character Sets

Teradata Database International Character Set Support

brand
Software
prodname
Teradata Database
vrm_release
15.00
15.10
category
Configuration
User Guide
featnum
B035-1125-015K

Teradata translation codes for the following client character sets are permanently enabled:

  • “ASCII Client Character Set Support” on page 25.
  • “EBCDIC Client Character Set Support” on page 26.
  • “UTF8 Client Character Set Support” on page 27.
  • “UTF16 Client Character Set Support” on page 28.
  • To use a client character set supported by permanently enabled Teradata translation codes, specify it as the client default. See “System Determination of Client Character Set” on page 55.

    Teradata also provides translation codes for support of these additional client character sets. However, you must enable each translation code you want to use before setting it as the client default. See “Enabling a Client Character Set” on page 55.

     

    Type

    Name

    Japanese Client Character Set Support

  • KATAKANAEBCDIC
  • KANJIEBCDIC5035_0I
  • KANJISJIS_0S
  • KANJIEBCDIC5026_0I
  • KANJIEUC_0U
  • KANJI932_1S0
  • Chinese Character Sets

  • SCHEBCDIC935_2IJ
  • TCHEBCDIC937_3IB
  • SCHGB2312_1T0
  • TCHBIG5_1R0
  • SCHINESE936_6R0
  • TCHINESE950_8R0
  • Korean Character Sets

  • HANGULEBCDIC933_1II
  • HANGULKSC5601_2R4
  • HANGUL949_7R0
  • Single-Byte International Character Sets

  • THAI874_4A0 (Thai)
  • LATIN1250_1A0
  • Includes: Czech, Croatian, Albanian, Hungarian, Polish, Romanian, and Serbian

  • CYRILLIC1251_2A0 (Cyrillic and Russian)
  • HEBREW1255_5A0
  • ARABIC1256_6A0
  • LATIN1254_7A0 (Turkish)
  • LATIN1258_8A0 (Vietnamese)
  • LATIN1252_3A0
  • LATIN1252_0A
  • The DBC.CharTranslationV view lists the client character sets for which Teradata supplies translation codes, and shows the code sequences the system uses to translate character data for each set from client form to server form and from server form back to client form.

    The character set list in DBC.CharTranslationV does not include ASCII, EBCDIC, UTF8 and UTF16, for which the Teradata translation codes are permanently enabled. For an example, see “About the DBC.CharTranslationsV View” on page 53.

    Note: You can create custom (site-defined) character sets, but you must add the names of any custom character set to DBC.CharTranslationV before you can enable and use it. See Chapter 5: “Site-Defined Client Character Sets.”

    To be usable, a client character set must compatible with the applicable default server character set.

    The default server character set is determined in the following hierarchical order. If a default is not defined, the system defers to the next lower item on the list:

    1 Table column default character set

    2 User default character set

    3 System (global) default character set.

    Note: The current system default is defined in the DBSControl DefaultCharacterSet field.

    For more information about defining the default server character set, see “Specifying the Default Server Character Set” on page 62.

    The following table lists client-server character set compatibilities:

     

    If the default server character set is...

    The client character set can be...

    LATIN

  • ASCII
  • EBCDIC
  • EBCDIC037_0E
  • EBCDIC277_0E
  • EBCDIC273_0E
  • LATIN1_0A
  • LATIN9_0A
  • LATIN1252_0A
  • A simple site-defined ASCII-based character set
  • Note: Do not use client character sets other than those listed to insert data into a LATIN column, even if the character set appears to be represented in LATIN (for example, Turkish). The system may incorrectly translate such characters when converting them to UNICODE.

    UNICODE

    Any valid single- or multibyte client character set.

    KANJISJIS

    KANJISJIS supports mixed single and multibyte characters and its form-of-use is identical with that of its client character set analog

    GRAPHIC

    Multibyte characters from the defined Graphic repertoire of the following character sets:

  • KanjiEBCDIC
  • KanjiSJIS_0S
  • KanjiEUC_0U
  • The following table provides general guidelines for choosing client character sets, based on how each set functions on certain client types.

     

    IF the client type is …

    THEN the client character sets that may work best are …

    Mainframe

  • EBCDIC
  • EBCDIC037_0E
  • KANJIEBCDIC5026_0I
  • KANJIEBCDIC5035_0I
  • KATAKANAEBCDIC
  • SCHEBCDIC935_2IJ
  • TCHEBCDIC937_3IB
  • HANGULEBCDIC933_1II
  • Network connected, running the UNIX® operating system

  • ASCII
  • KANJIEUC_0U
  • LATIN1_0A
  • LATIN9_0A
  • UTF8
  • SCHGB2312_1T0
  • TCHBIG5_1R0
  • HANGULKSC5601_2R4
  • Network connected, running the Windows operating system

  • ASCII
  • KANJISJIS_0S
  • LATIN1252_0A
  • UTF8
  • UTF16
  • SCHGB2312_1T0
  • TCHBIG5_1R0
  • HANGULKSC5601_2R4
  • SCHINESE936_6R0
  • HANGUL949_7R0
  • TCHINESE950_8R0
  • KANJI932_1S0
  • THAI874_4A0
  • LATIN1250_1A0
  • CYRILLIC1251_2A0
  • LATIN1252_3A0
  • HEBREW1255_5A0
  • ARABIC1256_6A0
  • LATIN1254_7A0
  • LATIN1258_8A0