Teradata SQL Error and Failure Codes from Error 3124 To 3132

3124 Internal error: FCF is not inside a user-generated transaction.
Explanation: This error occurs if the FCF is not inside a user-generated transaction.
Generated By: Dispatcher.
For Whom: System Support Representative.
Notes: This is a parser problem.
Remedy: Contact your support representative.

3125 Dispatcher fault isolation session threshold was exceeded.
Explanation: The threshold was exceeded for the count of all allowable fault isolation occurrences at the session level.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Save the system dump that caused the crash for analysis and report the problem to your support representative.

3126 Parser response to TDP has problem.
Explanation: This error occurs if the response to a TSP step is not a TSPSpoilD message.
Generated By: Dispatcher.
For Whom: System Support Representative.
Notes: This is a parser problem.
Remedy: Contact your support representative.

3127 Transaction aborted due to lock conflict with Queue Table Manager.
Explanation: When the Queue Table manager requires to refresh its cache, it will submit a row collection process which
needs a read lock on the table. If the lock cannot be obtained for a long while, the Queue Table manager will abort all
SELECT AND CONSUME statements that are in the wait state for that table. The intention is to allow the collection to proceed
by blowing away the transaction(s) which is/are potentially holding up the collection process.
Generated By: Dispatcher.
For Whom: End Users.
Remedy: Resubmit the aborted transaction as needed.

3128 Transaction aborted due to exceeding the maximum consume statement limit.
Explanation: This error occurs when there are too many SELECT AND CONSUME statements running concurrently.
The system maximum for SELECT AND CONSUME statements is 20% of the session limit for the system. A limit is
imposed because the SELECT AND CONSUME statement may enter a wait state holding up a session.
Generated By: Dispatcher.
For Whom: End Users.
Remedy: Resubmit the aborted transaction after other SELECT AND CONSUME statements are released.

3129 Internal error: Invalid category in initiation.category.
Explanation: The Parser has generated a message category in the step that the dispatcher did not expect.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Contact your support representative.

3130 Response limit exceeded.
Explanation: There is a TDBMS limit of 16 outstanding responses for a single session. If responses are allowed to pile up
by an application, this error will occur. A response is the response set from a SELECT statement. A response is kept by the
TDBMS until we know the user is done with it at which point it is cancelled. There are two scenarios:
1. If KeepResp is OFF, the response is automatically cancelled when all rows have been returned to the application and the
host has been notified of the end of the response.
2. If KeepResp is ON, the response is held until explicitly cancelled by the user.
In each case, the response can be explicitly cancelled by the application.as soon as it is no longer needed.
Generated By: Dispatcher.
For Whom: End user.
Remedy: The responses are the property of the session and will automatically automatically be cancelled if the session is
logged off. Cancel an old response and resubmit the request or transaction.

3131 The system time has been set.
Explanation: This is an informational message which will appear in the errorlog/eventlog whenever a host successfully
sets the system time. The old time, new time and logical host id of the host which caused the time to be set is included in the
logged data.
Generated By: Dispatcher.
For Whom: Not applicable.
Remedy: Not applicable.

3132 Access Logging step has failed. The transaction was aborted.
Explanation: The user has been flagged for Access Logging and an Access Logging step has failed. The original AMP
error code for the failed step is returned in the Info field of the Error or Failure parcel. The user’s transaction has been
aborted.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Examine the Info field of the Error or Failure parcel to determine why the Access Log step failed, then decide
on a course of action. If no Info field nor Failure parcel is attached to the error message (error message from Fastload or
Multiload), resubmit the job.

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