Teradata SQL Error and Failure Codes from Error 3189 To 3205

SQLServerF1_Header_Small

3189 Utility %VSTR does not exist.
Explanation: A console supervisor START command contains the name of a non-existent utility.
Generated By: ScpTask.
For Whom: End User.
Remedy: Correct the spelling of the utility name and retry the START command.

3190 Access to utility %VSTR denied.
Explanation: A console supervisor START command contains the name of a utility that exists, but the system administrator
has not granted you permission to execute the utility.
Generated By: ScpTask.
For Whom: End User.
Remedy: Have the system administrator grant you execute rights on the appropriate utility.

3191 Utility is not reading. DATA parcel ignored.
Explanation: The host application driving the console interface tried to send a DATA parcel when no ReadLn was pending
from the utility.
Generated By: ScpTask.
For Whom: End User if the end user has provided the host application part. Support Representative if the error is
returned from a Teradata provided host application.
Remedy: Await arrival of a PROMPT parcel and try to send the DATA parcel again.

3192 No utility partitions available. Try later.
Explanation: The console supervisor has run out of “slots” where utilities can be run.
Generated By: ScpTask.
For Whom: End User.
Remedy: Wait until some other user’s utility exits and try again.

3194 Failed to start utility %VSTR, Please try later.
Explanation: This error is returned to end user when the call to prginvoke() fails to start utility in given partition. This
could happen when DBS is heavily loaded.
Generated By: ScpTask, ScpRun.
For Whom: End User.
Remedy: Retry when DBS is not heavily loaded. If the problem persists for a long time, contact your Support Representative.

3199 Teradata has been restarted as requested by the user.
Explanation: This message is displayed to tell the user that the DBC has been restarted as a result of submitting the command:
DIAGNOSTIC DISTEST … CRASH
Generated By: Dispatcher.
For Whom: End User.
Remedy: Not applicable.

3200 Fatal error in Dispatcher.
Explanation: The Dispatcher encountered an error that cannot be fault isolated, and therefore a system restart is initiated.
Re-submitting the operation will probably cause another system crash.
Generated By: Dispatcher.
For Whom: End User, System Support Representative.
Remedy: Save the request that caused the crash, and contact your support representative.

3201 Statement caused Dispatcher stack overflow.
Explanation: The request was more complex than the Teradata SQL Dispatcher could process.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Simplify the statement if possible, and resubmit the request.

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

3204 SQL request completed ahead of Log request in the Dispatcher.
Explanation: The Dispatcher detected that the SQL request processing was completed ahead of Access Log processing.
An attempt will be made to isolate the fault.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Save the request that caused the problem, and contact your support representative.

3205 Message received has an invalid message kind.
Explanation: While the Dispatcher was processing a request, a message with an invalid message kind was encountered.
An attempt will be made to isolate the fault.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Save the request that caused the problem, and contact your support representative.

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