15.10 - Implementing Extended Character Sets - Teradata Database

Teradata Database International Character Set Support

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

To implement an extended site-defined client character set, you must create an entry in DBC.CharTranslationsV and a corresponding mapping file.

To define an extended site-defined client character set, you must create an entry in DBC.CharTranslationsV.

Follow the rules and procedures in “Implementing Custom Character Sets” on page 72, with the following exceptions:

  • The name of the character set follows the conventions described in “Naming Character Sets” on page 83.
  • Rather than mapping the client character set to the LATIN or KANJI1 internal form, the mapping is defined in terms of an internal transition form.
  • For all extended site defined client character sets, the E2IUp and I2EUp fields in DBC.CharTranslationsV are ignored; the uppercase properties of the character set are derived automatically.
  • You must also create a corresponding file on every node in one of the following directories in Teradata Database:

  • TPA etc
  • You can identify the location of the directory by using pdepath -e on the command line.

  • TPA cfg
  • You can identify the location of the directory by using pdepath -c on the command line.

    If the mapping file is stored in the TPA etc directory, during version change, any changes to this mapping file are lost. To avoid losing the changes, the best practice is to store the mapping and collation files in the TPA cfg directory, which is not updated during the installation of a new version of Teradata.

    A map file definition in the cfg overrides the definition in etc.

    The file defines the mapping between an internal transition form and Unicode for the character set. A single definition file may be used to support multiple client character sets. For example, if there is a need to handle both extended EBCDIC and extended ASCII character sets for support of the language, a single file may be used to define the internal transitional form. Two entries might be placed in the DBC.CharTranslationsV view that define the conversion between the client character set and the internal transitional form.