Teradata SQL Error and Failure Codes from Error 3413 To 3426

3413 A specified host does not exist.
Explanation: The host id specified in the start request parcel was not found.
Generated By: Resolver Base Module.
For Whom: End User.
Remedy: Verify the host id and resubmit the start request parcel.

3414 Invalid host character set.
Explanation: The host character set specified in the message header is invalid.
Generated By: Resolver Base Module.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

3415 An active request exists for this session.
Explanation: The Resolver Base Module already has an active request under the specified session number.
Generated By: Resolver Base Module.
For Whom: End User.
Remedy: Wait for the active request to finish and resubmit this request.

3416 This request has been aborted.
Explanation: This message indicates that an abort of the request was initiated by the user.
Generated By: Resolver Base Module.
For Whom: End User.
Remedy: None.

3417 An unknown error code has been generated by the Resolver Base Module.
Explanation: The Resolver Base Module is unable to retrieve the error message from the table DBC.ErrorMsgs based on
an error code generated internally.
Generated By: Resolver Base Module.
For Whom: Support Representative.
Remedy: Verify the DBC.ErrorMsgs table has been loaded (via DIPERRS). Save all information. Contact your Support
Representative.

3418 Invalid logoff flag in the request parcel.
Explanation: The logoff flag in the start request parcel was not 0 or 1.
Generated By: Resolver Base Module.
For Whom: End User.
Remedy: Change the logoff flag to 1 to logoff the resolved sessions, or change it to zero.

3419 Run Unit Id not found or does not have an in-doubt transaction.
Explanation: The run unit id listed in the start request parcel was not found, or the session did not have an in-doubt
transaction.
Generated By: Resolver Base Module.
For Whom: End User.
Remedy: Check the in-doubt transactions and their run unit ids. Remove the offending run unit id and resubmit the
request.

3420 The macro DBC.TWOPCRULE does not exist.
Explanation: The DBC.TwoPCRule macro was not installed and the user attempted to log onto the Resolver Base Module.
Generated By: Resolver Base Module.
For Whom: System Administrator.
Note: User must have the EXECUTE privilege on a macro called DBC.TwoPCRule. If the macro does not exist, or the user
does not have the EXECUTE privilege, the logon will fail.
Remedy: Verify that the macro exists on the system. The macro DBC.TwoPCRule can be created by running DIPVIEWS.
Save all information, then contact your Support Representative.

3421 RBM failed to insert a row to DBC.InDoubtResLog.
Explanation: This error occurs if the Resolver Base Module is unable to insert a row in the audit trail table,
DBC.InDoubtResLog.
Generated By: Resolver Base Module
For Whom: System Administrator.
Remedy: Verify the table exists. The table DBC.InDoubtResLog can be created by running the DIPVIEWS. Save all information,
then contact your Support Representative.

3425 Internal error: Internal error detected by RBM.
Explanation: The Resolver Base Module has determined that the DBC has handled a request incorrectly.
Generated By: Resolver Base Module
For Whom: Support Representative.
Remedy: Save all information. Contact your Support Representative.

3426 Internal error: An unknown thread state inside the RBM.
Explanation: The Resolver Base Module has received a thread with an unknown state from the Multi-Threaded Kernel.
Generated By: Resolver Base Module
For Whom: Support Representative.
Remedy: Save all information. Contact your Support Representative.

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