Client Character Sets - Parallel Data Pump

Teradata Parallel Data Pump Reference

Product
Parallel Data Pump
Release Number
15.00
Language
English (United States)
Last Update
2018-09-27
dita:id
B035-3021
lifecycle
previous
Product Category
Teradata Tools and Utilities

Client Character Sets

Standard Character Sets

Table 2 lists the standard character sets which are supported by Teradata Database.

 

Table 2: Standard Character Sets 

Standard Character Sets

System Configuration

Name

MainframeAttached

EBCDIC

NetworkAttached

ASCII

The terms ASCII and EBCDIC are often used in ambiguous ways, and this presents a difficulty for accented and non‑Latin characters. The user should select a client character set that exactly matches the character set that the import data uses.

If accented and non‑Latin characters are used, do not use the ASCII or EBCDIC client character sets. Instead, load and use one of the other Teradata‑supplied character sets, or a site‑defined character set that exactly matches the application character set, such as: EBCDIC037_0E for mainframe‑attached clients (for the United States or Canada), LATIN1_0A, LATIN9_0A (for Western European languages), LATIN1252_0A for Western European Microsoft® Windows clients, or UTF‑8 for UNIX system‑based clients.

Japanese Characters Sets

Table 3 lists the Japanese character sets which are supported by Teradata Database.

 

Table 3: Japanese Character Sets 

Japanese Character Sets

System Configuration

Character Set Name

MainframeAttached

KATAKANAEBCDIC

 

KANJIEBCDIC5026_0I

 

KANJIEBCDIC5035_0I

NetworkAttached

KANJIEUC_0U

 

KANJISJIS_0S

For more information on kanji character sets, refer to International Character Set Support (B035‑1125).

Notice:

Teradata TPump statements do not accept object names specified in internal database hexadecimal form and do not display object names in hexadecimal form.

Chinese and Korean Character Sets

Chinese and Korean character sets are available for mainframe‑ and network‑attached client systems.

Table 4 lists the Chinese character sets:

 

Table 4: Chinese Character Sets 

Chinese Character Sets

System Configuration

Name

MainframeAttached

SCHEBCDIC935_2IJ

 

TCHEBCDIC937_3IB

NetworkAttached

SCHGB2312_1T0

 

TCHBIG5_1R0

Table 5 lists the Korean character sets:

 

Table 5: Korean Character Sets 

Korean Character Sets

System Configuration

Name

MainframeAttached

HANGULEBCDIC933_1II

NetworkAttached

HANGULKSC5601_2R4

Rules for Using Chinese and Korean Character Sets

Certain rules apply when using Chinese and Korean character sets on mainframe‑ and network‑attached platforms.

  • Object Names
  • Teradata Database supports multi‑byte characters in object names when the client session character set is UTF‑8 or UTF‑16. For a list of valid and non‑valid characters when multi‑byte object names are used, see International Character Set Support (B035‑1125).

    If multi‑byte characters are used in object names in Teradata TPump script, they must be enclosed in double quotes.

  • Maximum String Length
  • Teradata Database requires two bytes to process each of the Chinese or Korean characters. This limits both request size and record size. For example, if a record consists of one string, the length of that string is limited to a maximum of 32,000 characters or 64,000 bytes.