Teradata SQL Error and Failure Codes from Error 3299 To 3311

SQLServerF1_Header_Small

3299 Invalid PE Vproc Number.
Explanation: The PE Vproc No specified in the request is not a valid PE Vproc No or the PE Vproc is offline.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3300 Invalid Scope.
Explanation: The Scope specified is invalid.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3301 Target WD is invalid or inactive.
Explanation: WD id specified as input parameter is invalid or inactive.
Generated By: Dispatcher task.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3302 TDWM information is not available.
Explanation: The PMPC command submitted requires a TDWM capability that is currently not available. This could be
a category that is not enabled or that the entire TDWM feature is not being used.
Generated By: Dispatcher task.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3303 This is a load utility session.
Explanation: TDWM WD ASSIGNMENT with REQUEST scope is not allowed on a load utility session.
Generated By: Dispatcher task.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

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

3306 The request cannot be released or aborted.
Explanation: The specific request specified cannot be released or aborted. This could be a request for Replication which
is controlled internally.
Generated By: Dispatcher task.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3307 Invalid TDWM Rule specification. %VSTR
Explanation: An attempt to specify a TDWM Rule dynamically was done with invalid parameters for a rule specification.
Generated By: Dispatcher task.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3308 Invalid TDWM Object specification. %VSTR
Explanation: An attempt to specify a TDWM Object dynamically was done with invalid parameters for an object specification.
Generated By: Dispatcher task.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3309 Invalid TDWM request specified. %VSTR
Explanation: The TDWM message command was given an invalid request type or an invalid user/password was specified.
Generated By: Dispatcher task.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3310 TDWM Control operation already in process
Explanation: TDWM Control operation is currently in process. Wait for this operation to complete before attempting
another operation.
Generated By: Dispatcher task.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3311 Invalid TDWM control parameters
Explanation: The request type, config id, or other TDWM control parameter value is invalid.
Generated By: Dispatcher task.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

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