17.20 - Mapping File - 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

You must also create a corresponding file on every node in one of the following directories in Analytics 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.