16.20 - Object Names - Teradata Vantage NewSQL Engine

Teradata Vantage™ NewSQL Engine International Character Set Support

prodname
Teradata Database
Teradata Vantage NewSQL Engine
vrm_release
16.20
created_date
March 2019
category
Configuration
User Guide
featnum
B035-1125-162K

Object names on systems enabled with Japanese language support can contain single-byte Latin and Katakana characters from the JIS X 0201 standard, and double-byte characters from the JIS X 0208 standard.

The valid ranges for JIS X 0201 characters in object names under the KanjiEUC client character set appear in rows cs0 and cs2 in KanjiEUC Code Set Localization. The set does not permit Katakana symbols 0x8EA1—0x8EA5 nor Unicode symbols other than $, #, and _.

The valid ranges for JIS X 0208 characters in object names under the KanjiEUC client character set appear in row cs1 in KanjiEUC Code Set Localization. Characters in the reserved regions of the standard are not allowed.

Characters from JIS X 0212 (row cs3) are not valid in object names. Additionally, some characters that are valid in JIS X 0208 do not map to the KanjiEBCDIC encoding and are not valid in KanjiEUC object names. The following table provides a complete list of multibyte character codes that are not valid for object names under the KANJIEUC_0U character set.

First Byte Second Byte Third Byte
0xA1 0xA1 - 0xAA 0xAD - 0xB1  
0xB3 - 0xBB 0xBD - 0xEF  
0xF1 - 0xF3 0xF5 - 0xFE  
0xA2 0xA1 - 0xFE  
0xA6 - 0xA8 0xA1 - 0xFE  
0xF4 0xA5 - 0xA6  
0x8E 0xA1 - 0xA5  
0x8F 0xA1 - 0xFE 0xA1 - 0xFE

For information on the rules and restrictions for naming Teradata Database objects, see the topics beginning with About Object Names.

Also see Teradata Vantage™ SQL Fundamentals, B035-1141, which covers topics such as:
  • Translation conventions for storing object names in the data dictionary
  • Rules for object name comparison