Teradata SQL Error and Failure Codes from Error 3133 To 3147

SQLServerF1_Header_Small

3133 Default Character Set is invalid.
Explanation: The default character set name specified for the Host is not translatable to a valid character set. Either the
character set name does not exist in the DBC.Translation table or the TranslateId specified for that character set name is
invalid.
Generated By: Dispatcher.
For Whom: System Administrator.
Remedy: Check that the Character Set Name exists in the DBC.Translation table and, if it does exist, that the TranslateId
is within the valid range.

3134 The request was aborted by an ABORT SESSION command.
Explanation: This error is returned to the user because the Dispatcher has received an ABORT SESSION request from
the Monitor Task.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Contact System Operation to determine why the ABORT SESSION was directed against your session.

3135 Internal Error: The abort request was not locked by the Monitor task.
Explanation: This error occurs because the abort request has not been locked and forces the Dispatcher to crash.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Contact your support representative.

3136 Internal Error: The request cannot be aborted, session is in-doubt.
Explanation: The request cannot be aborted because the session is in the in-doubt state. This error causes a system
restart.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Save all information. Contact your support representative.

3137 Internal Error: The request is already committed and cannot be aborted.
Explanation: A committed request cannot be aborted. The Dispatcher halts the system.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Save all information. Contact your support representative.

3138 Waiting to load in-doubt session information
Explanation: The in-doubt information has not yet been loaded by the AMPs.
Generated By: Dispatcher.
For Whom: System Administrator.
Remedy: Wait until the in-doubt information is loaded, then resubmit the request.

3140 Request has already been committed
Explanation: The request has been committed.
Generated By: Dispatcher.
For Whom: System Administrator.
Remedy: None – request has been committed.

3142 An informative Dispatcher event was logged.
Explanation: The event message documents the specific information.
Generated By: Dispatcher request processing.
For Whom: System Administrator.
Remedy: The 3142 event code is only logged in the error log and is not returned to the end user. Based on the specific
information that is logged, it may be necessary to contact your support representative. In general, this message is for information
only.

3144 Dispatcher fault due to a fault injection test.
Explanation: The transaction was aborted due to a fault injection test.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: None required.

3145 The request was aborted by a ROLLFORWARD operation.
Explanation: This error is returned to the user because the Dispatcher has received an abort session request. The abort
was initiated by an AMP against all sessions blocking a RollForward operation.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Disable the RollForward with Row Hash Locks feature by setting the RollForwardLock field to FALSE in the
DBS GDO and re-submit the request.

3146 Config response was compromised due to unknown error.
Explanation: This is a notice of serious inconsistencies between system configuration. The Distpatcher could not read
either the VPROC-ID or the PMA from VCONFIG.GDO. The GDO could have been too big, or unreadable. The DBS is
forced to bypass those portion of the config response to avoid crashing the system.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Check the TDP and all client connections to see if they could still connect to the DBS. If no failure wait for an
opportunity to do a TPARESET. If this error keeps appearing, notify your support representative immediately.

3147 Expected session cannot be located at dispatcher worker task.
Explanation: The Dispatcher’s session context was supposed to contain this session but it does not. This may occur
while Session control was trying to forward a SET SESSION ACCOUNT message to the dispatcher worker task that was
working on behalf of this session or the message was forwarded, but the session context no longer exists in dispatcher
worker task.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Check Session Table, and if everything was fine, contact your support representative.

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