Usage Notes - Teradata VantageCloud Lake

Lake - Database Reference

Deployment
VantageCloud
Edition
Lake
Product
Teradata VantageCloud Lake
Release Number
Published
February 2025
ft:locale
en-US
ft:lastEdition
2025-11-21
dita:mapPath
ohi1683672393549.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
ohi1683672393549

If client system connections are to use the defined character sets, the system administrator specifies which character set is assigned to which client system (see HostsInfoV). Otherwise, the standard default is used. Also, the user may specify a defined character set after a session is started (see CharSetsV).

When specifying a character set for a session, the choice must be compatible with the internal code of the logon client system; that is, an EBCDIC-compatible character set for sessions initiated from an IBM mainframe, ASCII-compatible sets for all others.Therefore, Teradata recommends using a convention for naming character sets which differentiates between EBCDIC and ASCII compatibility (see Example: Using CharTranslationsV).

CharSetId

If the character set is user-defined, the ID must also exist in DBC.CharTranslations.CharSetID.

For constraints not involving comparison of character data or not using CHARSET_COLL for evaluation, the value is NULL.

InstallFlag

The database must be reset to install the rows containing a Y in the InstallFlag field. If the value of InstallFlag is Y in 12 rows or fewer, each Y row is loaded. If InstallFlag is Y in more than 12 rows, then the CharSetName values are sorted in ascending ASCII sequence, and rows are loaded in alphabetical order until 12 sets are installed or the names are exhausted.