Alternate Character Set Support - Teradata Tools and Utilities

Teradata® Archive/Recovery Utility Reference

Product
Teradata Tools and Utilities
Release Number
16.20
Published
March 2019
Language
English (United States)
Last Update
2019-06-05
dita:mapPath
fac1527114221922.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2412
Product Category
Teradata Tools and Utilities

Teradata ARC runs on IBM mainframes, which use the kanjiEBCDIC character set. However, object names created in kanji character sets (UNIX OS or MS/DOS platforms) other than EBCDIC can be copied from archive, but not translated into internal RDBMS format names.

The reason for this is that “hybrid” EBCDIC and kanjiEUC, or EBCDIC and kanjiShiftJIS single byte and multibyte characters cannot be translated into internal RDBMS format. If the object name is in internal RDBMS format, the Teradata Database can translate it into an external client format name.

Hybrid object names result when archiving an object created in the KANJIEUC or KANJISJIS character set from a KANJIEBCDIC mainframe client and the hexadecimal representation of the object being archived is not used. In such a circumstance, the Teradata Database cannot properly translate the character set and produces a hybrid object name composed of single byte characters from the EBCDIC character set and multibyte characters from the creating character set (UNIX OS or DOS/V). The hybrid object name cannot be understood by the Teradata Database. Correct this in one of two ways:
  • Use the internal hexadecimal object name, in format (’......’XN). This is the preferred method.

    The ARCMAIN program uses Teradata Database to translate the internal hexadecimal format names to external hexadecimal format for the purpose of searching the archive file.

  • If the internal hexadecimal object name is unknown:
  1. Run the ANALYZE statement on the archive tape without making a connection to the Teradata Database by means of the LOGON statement.
  2. ANALYZE identifies the database in a hybrid format of the name.
  3. Use the hybrid format of the name in the “FROM” syntax to specify that the object name in the archive file is different from the name of the target object name.