17.10 - Error - Call-Level Interface Version 2

Teradata® Call-Level Interface Version 2 Reference for Workstation-Attached Systems

Call-Level Interface Version 2
Release Number
October 2021
English (United States)
Last Update


Returned in response to a request that resulted in a non-database-related error.

Usage Notes

If the request is in a transaction, then the transaction is not aborted.

The invalid request can be corrected and resubmitted.

For example, the Error parcel might inform an application that the byte count in the Resp or KeepResp parcel is too small to contain a parcel (error code 3116); in this case, the application should reallocate the input (response) buffer, rebuild and resubmit the request.

This parcel is generated by the Teradata server.

Parcel Data

The following table lists field information for Error.

Flavor Parcel Body Length Parcel Body Fields
49 8 to 263
  • StatementNo:
  • Info:
  • Code:
  • Length:
  • Msg:
  • 2-byte unsigned integer
  • 2-byte unsigned integer
  • 2-byte unsigned integer
  • 2-byte unsigned integer
  • 1 to 255 bytes

Field Notes

Error Parcel field definitions are as follows:
  • StatementNo is the number of the Teradata SQL statement in the Teradata SQL request that failed.
  • Info is an integer value whose use depends upon the error code returned. For its contents, look up the error code in Teradata Vantage™ - Database Messages, B035-1096.
  • Code is the error code specifying the type of error that occurred.
  • Length is the total number of bytes in the textual representation of the error code. If Length = 0, no textual representation of the error is present.
    Msg is the error message in character format.