Exception Handling | Character Set | VantageCloud Lake - Exception Handling - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
ft:locale
en-US
ft:lastEdition
2024-12-11
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

Conversion of character data type between a client form-of-use and the VantageCloud Lake form-of-use may encounter the following exception.

Type Description See
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
Conversion exception A conversion exception occurs when there is no character in the target repertoire that corresponds to a character from the source string.
Truncation exception A truncation exception occurs when the source cannot fit into the target field without truncation of a non-pad character. Truncation Exceptions

For information on how exceptions are handled in sessions where Unicode Pass Through is enabled, see UNICODE PASS THROUGH.

Exception Precedence

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.

Errors and Transaction Modes

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

An ANSI mode session follows the ANSI transaction semantics.

Errors and Load Utilities

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. Analytics Database records the field that caused the problem, and the load utility is allowed to proceed.