15.10 - Exception Handling - Teradata Database

Teradata Database International Character Set Support

Teradata Database
User Guide

Conversion of character data type between a client form-of-use and the Teradata Database form-of-use may encounter exception situations.

There are three possible exceptions.





Illegal client data form-of-use

An illegal form-of-use occurs when the client data violates the structure of the client form-of-use, for example, an unmatched SI character in KanjiEBCDIC.

“Illegal Form-of-Use” on page 138

Conversion exception

A conversion exception occurs when there is no character in the target repertoire that corresponds to a character from the source string.

  • “E2I Conversion Exceptions” on page 139
  • “I2E Conversion Exceptions” on page 140
  • Truncation exception

    A truncation exception occurs when the source cannot fit into the target field without truncation of a non-pad character.

    “Truncation Exceptions” on page 143

    There is no precedence of one exception over the other. When the illegal form-of-use, truncation-exception, and conversion-exception occur simultaneously, whichever exception is recognized first is the one reported.

    For an SQL session operating in Teradata mode, an error aborts the current transaction.

    An ANSI mode session follows the ANSI transaction semantics.

    In the case of the load utilities (MultiLoad and FastLoad), the offending record is placed into the error tables used by that utility.

    The offending characters, rather than any error characters, are stored in the error tables. The Teradata Database records the field that caused the problem, and the load utility is allowed to proceed.