Responding to Error and Failure Parcels - Call-Level Interface Version 2

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

Product
Call-Level Interface Version 2
Release Number
15.10
Language
English (United States)
Last Update
2018-10-07
dita:id
B035-2418
lifecycle
previous
Product Category
Teradata Tools and Utilities

The guidelines for responding to the Error and Failure parcel codes are shown in Table 40:

 

Table 40: Error and Failure Codes 

Code

Message

Action

Failure Code 2631

transaction aborted due to deadlock

Re-submit the transaction.

Failure Code 2639

sorry, too many simultaneous transactions

Re-submit the request.

Failure Code 2641

databasename.tablename was restructured. Resubmit transaction.

Re-submit the transaction.

Error Code 2825

no record of the last request was found after DBC restart

Re-submit the Teradata SQL request.

Error Code 2826

request completed but all output was lost due to DBC restart

Whether or not the original Teradata SQL request should be re-submitted to obtain the response depends on the nature of the request. For instance, if the request was to display certain data, the original request can safely be re-submitted; if the request was to multiply the values in a column by 10 and the request is re-submitted, the column will in effect have been multiplied by 100, so it is not safe to re-submit the original request.

Failure Code 2827

request was aborted by user or due to statement error

The circumstances may not warrant re-submitting anything at all; however, if re-submission is appropriate, re-submit the transaction.

Failure Code 2828

request was rolled back during system recovery

The transaction was lost due to a crash; re-submit the transaction.

Failure Code 2835

a unique index has been invalidated; resubmit transaction

Re-submit the transaction.

Failure Code 3111

the transaction has been timed out

Re-submit the transaction.

Error Code 3116

response buffer size is insufficient to hold one record

Enlarge the response buffer and then submit a fetch. This code should be taken care of by CLI in CLI. It should not be seen by the application.

Failure Code 3120

the request is aborted because of a DBC recovery

Re-submit the transaction.

Failure Code 3598

concurrent change conflict on data base -- try again

Re-submit the transaction.

Failure Code 3603

concurrent change conflict on table -- try again

Re-submit the transaction.

Failure Code 3897

request aborted due to DBC system crash. Resubmit

Re-submit the transaction.

If any other code appears, stop the program and investigate the problem.

The official list of valid codes is in the Messages (B035‑1096) manual.