Teradata SQL Error and Failure Codes from Error 3312 To 3322

3312 TDWM configuration is not running
Explanation: An Enable, Disable, or Apply operation can only be applied to the current TDWM configuration.
Generated By: Dispatcher task.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3313 TDWM control logon error. %VSTR
Explanation: The TDWM control operation failed because a logon failure occurred.
Generated By: Dispatcher task.
For Whom: System Operator.
Remedy: The TDWM database no longer exists, or the password has changed. Correct the error and resubmit the
request.

3314 TDWM database access error. %VSTR
Explanation: The TDWM control operation failed because an error occurred when reading the TDWM database.
Generated By: Dispatcher task.
For Whom: System Operator.
Remedy: Access to the TDWM database may be temporarily unavailable, or the configuration may be corrupted. If this
error persists, contact support.

3315 TDWM database version error. %VSTR
Explanation: The TDWM control operation failed because the database version is incompatible with the current TDWM
software.
Generated By: Dispatcher task.
For Whom: System Operator.
Remedy: The TDWM database should be migrated to the current version.

3316 TDWM configuration is invalid. %VSTR
Explanation: The TDWM control operation failed because the config id specified does not exist, or the TDWM dynamic
rule operation failed because the applicable rules category is not enabled.
Generated By: Dispatcher task.
For Whom: End user.
Remedy: Specify a valid config id and resubmit the request.

3317 TDWM rule name or owner invalid. %VSTR
Explanation: The TDWM dynamic rule operation failed because the rule name already exists for a create, or for other
operations the rule name does not exist or is not a dynamic rule.
Generated By: Dispatcher task.
For Whom: End user.
Remedy: Specify a valid config id and resubmit the request.

3318 Response message size is too small.
Explanation: Most of TDWM PM/PC commands do not support continue request. This means all response parcels
including End Request parcel must fit in one message. This error indicates the response message size specified is less than the minimum or it is too small to process all response parcels.
Generated By: Pfmustsk task.
For Whom: End user.
Remedy: Increase the response message size and resubmit the request.

3319 TDWM control command timed out.
Explanation: The TDWM control command, or command sequence in the case of dynamic rules, did not complete
within 5 minutes and was automatically timed out.
Generated By: Pfmustsk task.
For Whom: End user.
Remedy: Resubmit the request.

3320 Monitor Access Denied: Fatal Error Count Exceeded the Maximum
Explanation: The user is denied the logon because the number of fatal error count exceeded the maximum on the given
PE. When a fatal error is encountered in PfmUsTsk on the problem PE will try to abort the request and logoff the session.
On the third time an online PE sees the fatal error, it will abort the session and it will no longer allow logons onto that PE.
Only dbs restart will reset the fatal error count to zero.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Attempt to logon through a different PE that has not reached its Monitor session fatal count limit. Or schedule
a manual DBS restart.

3321 Monitor Subsystem Has Been Shut Down Due To Internal Error
Explanation: PM/PC Monitor Subsystem has been shut down due to an internal error in either PfmCoTsk or SesPMain
tasks. No PM/PC requests/ logons will be allowed until next dbs restart.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Schedule a manual DBS restart.

3322 TDWM internal error. %VSTR
Explanation: An internal software occurred which prevents TDWM from completing the request. Additional information
is provided in the error message, and 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.

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