Character Set Limitations - TARA/ABU

Using an alternate character set allows naming tables and databases using an extended set of characters. However, the internal representation of these extended characters depends on the session character set.

Although Teradata ARC can be used with a Teradata Database that uses an alternate character set, special care must be taken when archive and restore operations are used on a Teradata Database with an alternate character set:

When archiving objects with names that use non-Latin characters, use the same character set defined using the multinational collation option for the database.

Multinational collation provides more culturally aware ordering of data in the database. If a different character set is used, Teradata ARC might have difficulty restoring the archive. To learn more about multinational collation, refer to SQL Fundamentals.

To restore an archive made with an alternate character set, use the same character set used in the archive.

Do not restore an archive on a system that cannot handle the character sets used to create the archive.

When the KATAKANAEBCDIC character set is passed to Teradata ARC, all messages are uppercase because that character set does not support lowercase Latin letters.

Teradata ARC does not support the use of control characters (0x00 thru 0x1F) in object names.

Teradata ARC treats multi-byte character object names as case sensitive object names. This means that the user has to specify a multi-byte object name in the exact case that was used when the object was created in the Teradata Database, otherwise Teradata ARC may not be able to locate that object. Character sets which may contain multi-byte characters include any of the non-Latin character sets. The ASCII and EBCIDIC character sets are not included in this restriction.

When a Teradata ARC run begins while using an alternate character set, the software displays the following message, where character_set_name is the name of the character set defined in the runtime parameter:

CHARACTER SET IN USE: character_set_name

Note: Contact the system administrator or Teradata field support representative to learn more about the alternate character sets supported for the Teradata Database installation.

Limitations for Japanese Character Sets and Object Names

For certain character sets (including multibyte characters), Teradata ARC accepts non-Latin characters as part of an object name. An object name can be a database name, table name, user name, password, or checkpoint name in a Teradata ARC statement. Object names must be no longer than 30 characters.

Teradata ARC also supports input and display of object names in hexadecimal notation. Teradata Database can store and display objects in hexadecimal format to allow object names to be archived and restored from one platform to another. To learn more about using non-Latin characters in object names, refer to SQL Fundamentals.

For example, to archive a database created on a UNIX® platform from an IBM mainframe, do not specify the UNIX EUC character set on the IBM mainframe. Instead, specify the database name in the internal hexadecimal format understood by the Teradata Database.

The Teradata ARC allows specifying object names in any of these formats:

Without quotes. For example, for database DBC:

DBC

With quotes. For example, for database DBC:

“DBC”

External hexadecimal:

X’<object name in external hexadecimal format>’

This indicates that the specified hexadecimal string represents a name in the client (external) format. For example, for database DBC:

X’C4C2C3’

Internal hexadecimal

’<object name in internal hexadecimal format>’XN

This indicates that the specified hexadecimal string represents a name in the Teradata Database internal format. For example, for database DBC:

’444243’XN

A Teradata ARC statement can contain any combination of object name notations. For example, the hexadecimal notation is a valid object name:

   ’4142’XN.TABLEONE

Limitations for Chinese and Korean Character Sets and Object Names

When using Chinese and Korean character sets on channel- and network-attached platforms, object names are limited to:

A-Z, a-z

0-9

Special characters such as $ and _

No more than 30 bytes

Note: For more information on Chinese and Korean character set restrictions, refer to SQL Fundamentals.