Teradata SQL Error and Failure Codes from Error 3323 To 3401

3323 The TDWM Event is not defined.
Explanation: The event that was supplied in this request is not defined in the current rule set. An error should be logged in the DBC.TdwmEventLog table.
Generated By: Pfmustsk task.
For Whom: End user.
Remedy: Review logged error and resolve before attempting to resubmit the request.

3324 More data exists than was returned.
Explanation: This is a warning that there were more records to be returned than would fit into the response buffer.
Generated By: Pfmustsk task.
For Whom: End user.
Remedy: Increase the size of the response buffer if all records are desired.

3325 Invalid Threshold in MONITOR AWT RESOURCE.
Explanation: Invalid threshold has been specified as input argument of MONITOR AWT RESOURCE; PM/API command.
Thresholds must be defined in ascending order and cannot contain gaps. Thresholds that are not used must be set to -1. The minimum valid threshold is 0.
Generated By: Pfmustsk task.
For Whom: End user.
Remedy: Correct threshold value and resubmit the request.

3326 The session cannot be found.
Explanation: The specific session number supplied cannot be found.
Generated By: Dispatcher task.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3327 A utility session in delay queue has been aborted by Administrator or Operations Staff.
Explanation: Someone with the proper Access Right has completed executing an TDWM DELAY REQUEST CHANGE
Abort Utility Session option and the specified utility session in delay queue has been aborted and logged off.
Generated By: Dispatcher task.
For Whom: End User.
Remedy: None.

3328 An error occurred during data collection.
Explanation: An error occurred during data collection. This could be either one time error or persistent error. There may be a snapshot dump taken due to this error. Please check event or messages log. If this error persists the PFM subsystem may be disabled.
Generated By: PFMCoTsk and Pfmsmain tasks
For Whom: End User, Support Representative.
Remedy: Resubmit the request. Save all relevant information and the crash dump and notify your Support Representative.

3329 Query Band is in transition state. Please try again
Explanation: An error occurred during QueryBand retreival.
Generated By: ConTsk
For Whom: End User.
Remedy: Resubmit the request.

3330 Timed out request clean up is still in progress. Please try again in a few minutes.
Explanation: The clean up for previous timed out request has not completed.
When a request is timed out, there are pending response messages from other PMPC tasks. Timed out request clean up is
completed when all expected response messages are received. Until the response messages are received, new requests
would be delayed. Therefore to relieve congestion no new requests are permitted while the response messages for the
timed out request are outstanding. New requests are rejected with this error.
Generated By: pfmustsk task
For Whom: End User.
Remedy: Resubmit the request.

3331 The API is obsolete.
Explanation: The API is obsolete in the current release.
Generated By: pfmustsk task
For Whom: End User.
Remedy: Use a different API.

3400 Start request parcel does not contain all required fields.
Explanation: Not all required fields were present in the start request parcel. The start request parcel generally contains a
function code, a logoff flag, a logical hostid, a coordinator id and a session list.
Generated By: Resolver Base Module.
For Whom: End User.
Remedy: Reformat the parcel and resubmit the request.

3401 Invalid function code in the request parcel.
Explanation: This error occurs if the function code in the start request parcel was not 1-6. The function code is the first field of the Resolver Base Module start request parcel – possible values are: 1 – Return a list of in-doubt transactions. 2 -Commit all in-doubt transactions. 3 – Commit specific in-doubt transactions. 4 – Rollback all in-doubt transactions. 5 – Rollback specific in-doubt transactions. 6 – Return a list of coordinators.
Generated By: Resolver Base Module.
For Whom: End User.
Remedy: Change function code and resubmit.

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