Teradata SQL Error and Failure Codes from Error 3106 To 3115

SQLServerF1_Header_Small

3106 Either AMPStepsLength or RespStepsLength is bad in DSPHdr.
Explanation: This error occurs if the DSP message received from the Parser has a problem either with AMPStepsLength
or AMPRespsLength.
Generated By: Dispatcher.
For Whom: System Support Representative.
Notes: Check the DSPHdr of the message from the Parser.
Remedy: Contact your support representative.

3107 Internal error: BytesMoved does not match MsgSize.
Explanation: This error occurs if BytesMoved is greater than MsgSize in the DisSHost.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Contact your support representative.

3108 Message class is bad.
Explanation: This error occurs if the class of a message received from a mailbox is not appropriate.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Contact your support representative.

3109 Internal error detected by Dispatcher.
Explanation: One of the Dispatcher’s internal consistency checks has failed.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Save the information displayed with this error message and all associated dumps. Isolate the request that
causes this error. Report the problem to your support representative.

3110 The transaction was aborted by the user.
Explanation: This error occurs if a request is aborted by the user.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Correct the SQL statement and resubmit it.

3111 The Dispatcher has timed out the transaction.
Explanation: This error occurs if a request is timed out by the dispatcher. The 3111 is turned into a 2631 error (deadlock)
to be returned to the user so that it gets retried. Thus each 3111 in the error log should correspond to a 2631 received by an
application.
Generated By: Dispatcher.
For Whom: End User.
Notes: For some reason other than deadlock or user error, the user’s request is no longer using CPU time on any processor
in the system. The 3111 error is only logged in the error log and NOT returned to the end user.
Remedy: Resubmitting the request should work. If the condition recurs, contact your support representative.

3112 Error info logged after AMP step failure.
Explanation: This event occurs when display the failed request session information by the dispatcher.
Generated By: Dispatcher.
For Whom: System Engineer or Data Base Administrator.
Notes: The 3112 event code is only logged in the error log and NOT returned to the end user. There may also be a snapshot
dump associated. The event code 3112 will always display when there is an AMP failure with error code 7487.
Remedy: The request was aborted.

3113 SQL request text logged after AMP step failure.
Explanation: This event occurs if a failed request context present by the dispatcher.
Generated By: Dispatcher.
For Whom: System Engineer or Data Base Administrator.
Notes: The 3113 event code is only logged in the error log and NOT returned to the end user. If a request context exist in
the DSP storage this event code will be logged. It will also accompany by event code 3112.
Remedy: The request was aborted.

3114 Dispatcher internal error during access log processing. Please do not re-submit request.
Explanation: Access logging aspect of request processing encountered a fault. An attempt will be made to isolate the
fault.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Save the aborted request, and report the problem to to your support representative.

3115 Response buffer size is insufficient to hold one record 32KB.
Explanation: This error occurs if the minimum number of bytes that can be returned to the host is larger than the host
application has specified in a RESP or KEEPRESP parcel.
This occurs if user specifies a response buffer <= 32K but the actual data is > 32K. This is to prevent previous host utilities
from retry and also let 64KB-RowSize host utilities to act properly.
Generated By: Dispatcher.
For Whom: End User.
Notes: An entire row must be able to fit in the number of bytes specified in a RESP or KEEPRESP parcel.
The ERROR parcel in which this error is returned indicates the minimum buffer size required in the Info field.
The string “Message > 32K size and overflow user buffer!” is sometimes returned in lieu of the documented message text.
This alternate text has a meaning identical to the text documented for error 3115.
Remedy: For Host utilities that cannot handle 64KB Row Size, they should not resend the request.
For Host utilities that can handle 64KB Row Size, enlarge the application’s response buffer size to at least the size (but no
more than 64,256) returned in the Info field of the ERROR parcel and submit a CONTINUE request containing a single
RESP or KEEPRESP parcel that specifies the new response buffer size.
Please refer to the Call-Level Interface reference manual for instructions on how to change the response buffer size.

Above are list of Teradata Errors or Failure Codes from Error 3106 To 3115 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 *