15.10 - Error and Failure Codes - Call-Level Interface Version 2

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

prodname
Call-Level Interface Version 2
vrm_release
15.10
category
Programming Reference
featnum
B035-2417-035K

The application should save the current Teradata SQL request and any Teradata SQL request for which the response is being held on the Teradata Database, in case they must be resubmitted. If a transaction spans more than one request, all the requests should be saved, in case the transaction must be resubmitted.

The guidelines for responding to the error and failure parcel codes are listed in Table 46:

 

Table 46: Error and Failure Codes 

Code

Message

Action

Failure Code 2631

transaction aborted due to deadlock.

Resubmit the transaction

Failure Code 2639

sorry, too many simultaneous transactions.

Resubmit the request

Failure Code 2641

databasename.tablename was restructured.

Resubmit the transaction

Error Code 2825

no record of the last request was found after the Teradata Database restart.

Resubmit the Teradata SQL request

Error Code 2826

request completed but all output was lost due to the Teradata Database restart.

Whether or not the original Teradata SQL request should be resubmitted 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 resubmitted. If the request was to multiply the values in a column by 10 and the request is resubmitted, the column will in effect have been multiplied by 100, so it is not safe to resubmit the original request.

Failure Code 2827

request was aborted by user or due to statement error.

The circumstances may not warrant resubmitting anything at all; however, if resubmission is appropriate, resubmit the transaction

Failure Code 2828

request was rolled back during system recovery.

The transaction was lost due to a crash; resubmit the transaction

Failure Code 2835

a unique index has been invalidated; resubmit transaction.

Resubmit the transaction

Failure Code 3111

the transaction has been timed out.

Resubmit the transaction

Error Code 3115

a response parcel greater than 32767 bytes but the CLIv2 Maximum Parcel option to allow larger parcels was not specified.

Specify the Maximum Parcel option to allow larger parcels

 

an invalid value was returned by the server for the Error parcel information field, being either 0 or not greater than the existing buffer size.

Report the server problem to the Global Support Center

Error Code 3116

an invalid value was returned by the server for the Error parcel information field (being either zero or greater than 32767) when Maximum‑parcel was specified as O.

Report the server problem to the Global Support Center

Failure Code 3120

the request is aborted because of a Teradata Database recovery.

Resubmit the transaction

Error Code 3177

Maximum‑parcel was specified as 'O' but the server requires 'H', or an invalid value was returned by the server for the data in a MinimumResponseBuffer entry in an ErrorInformation parcel, or that parcel was missing or malformed.

If Maximum‑parcel was specified as 'H', report the server problem to Technical Support.

Failure Code 3598

concurrent change conflict on data base - try again.

Resubmit the transaction

Failure Code 3603

concurrent change conflict on table - try again.

Resubmit the transaction

Failure Code 3897

request aborted due to system crash. Resubmit.

Resubmit the transaction

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

The official list of retryable codes is in “Retryable Errors,” located in Messages (B035‑1096).