Teradata SQL Error and Failure Codes from Error 3402 To 3412

3402 Coordinator name is shorter than specified or the length is invalid.
Explanation: This error occurs if more bytes were specified than were contained in the coordinator id string, or the
length of the coordinator id is invalid.
Generated By: Resolver Base Module.
For Whom: End User.
Remedy: Change the length or the coordinator id and resubmit.

3403 Request parcel contains fewer session ids than specified.
Explanation: This error occurs if more session ids were specified than the parcel had room for. Either the length of the parcel, or the session count in the start request parcel is incorrectly specified.
Generated By: Resolver Base Module.
For Whom: End User.
Remedy: Reduce the number of session ids in the request parcel, or reduce the parcel length, and resubmit the request.

3404 No more output to send for the continue request.
Explanation: A continue request was sent, but the DBS had no more output.
Generated By: Resolver Base Module.
For Whom: End User.
Remedy: None necessary.

3405 Session %VSTR not found or does not have an in-doubt transaction.
Explanation: The specified session listed in the start request parcel was not found, or the session did not have an indoubt
transaction.
Generated By: Resolver Base Module.
For Whom: End User.
Remedy: Remove the incorrect in-doubt session id and resubmit.

3406 The RBM session %VSTR does not exist.
Explanation: This error occurs if the RBM session for the request was not found. The error is most likely due to a host
application programming error.
Generated By: Resolver Base Module.
For Whom: End User.
Remedy: Correct the session number and resubmit.

3407 A specified RBM request does not exist.
Explanation: The request was not found. The error is most likely due to a host application programming error.
Generated By: Resolver Base Module.
For Whom: End User.
Remedy: Correct the CLI request number and resubmit.

3408 Unable to access session %VSTR with in-doubt transaction.
Explanation: The Resolver Base Module could not access the session specified, possibly because the session is locked by
another DBS task.
Generated By: Resolver Base Module
For Whom: End User.
Remedy: Resubmit the request – the transaction may have been resolved. Display the list of sessions having in-doubt
transactions and verify.

3409 The parcel length is invalid.
Explanation: The parcel length specified does not agree with the expected value.
Generated By: Resolver Base Module
For Whom: End User.
Remedy: Correct the parcel length and resubmit the request.

3410 The input buffer size specified in the response parcel is too short.
Explanation: The input buffer size specified in the response parcel is too small to hold one record.
Generated By: Resolver Base Module
For Whom: End User.
Notes: The FAILURE parcel in which this error is returned indicates the minimum buffer size required in the information
field.
Remedy: Enlarge the input buffer to the size returned in the informatin field of this FAILURE parcel and resubmit the
request.

3411 The request parcel flavor specified is invalid.
Explanation: The flavor of the request parcel is invalid.
Generated By: Resolver Base Module
For Whom: End User.
Remedy: Check the parcel flavor and resubmit the parcel.

3412 The respond parcel flavor specified is invalid.
Explanation: The flavor of the respond parcel is invalid. For the Resolver Base Module, the flavor of the respond parcel must be either RESP or CANCEL.
Generated By: Resolver Base Module
For Whom: End User.
Remedy: Check the parcel flavor and resubmit the parcel.

Above are list of Teradata Errors or Failure Codes from Error 3402 To 3412 received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *