Teradata SQL Error and Failure Codes from Error 3177 To 3188

SQLServerF1_Header_Small

3177 Response buffer size is insufficient to hold one record 64KB.
Explanation: This error occurs if the minimum number of bytes that can be returned to the host is larger than what the
host application has specified in a RESP, EXTRESP, KEEPRESP or EXTKEEPRESP parcel. This occurs if user specifies a
response buffer <= 64KB but the actual data is > 64KB.
Generated By: Dispatcher.
For Whom: End User.
Notes: An entire response data must be able to fit in the number of bytes specified in a RESP, EXTRESP, KEEPRESP or
EXTKEEPRESP parcel. The ERROR parcel in which this error is returned indicates the minimum buffer size required in the
Info field as the number of 512B needed.
Remedy: For Host utilities that cannot handle 1MB Response buffer, they should not resend the request.
For Host utilities that can handle 1MB response buffer, the client should grow the buffer and send a ’Continue’ request with
the required buffer size. It should send the new size in EXTRESP (flavor 153) or EXTKEEPRESP (flavor 154) in the continue
message. For this error code, the Info field in the error parcel will have the number of 512 Bytes required for the buffer size.
The client should read this number, multiply by 512 and allocate the new buffer size.
Please refer to the Call-Level Interface reference manual for instructions on how to change the response buffer size.

3178 Queue Table Cache is full.
Explanation: The Queue Table Cache reached it’s memory limit of 1MB/PE. An unsuccessful attempt was made to spoil
other entries in the cache to make room for this request.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Wait until the completion of other requests and then resubmit the request.

3179 Select and Consume Request is obsolete.
Explanation: The waiting select and consume request is obsolete due to either the drop or restore of the queue table.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Resubmit the request after the queue table is present.

3180 Service console programming fault detected.
Explanation: This crash occurs when internal consistency checks fail within the host accessible console partition.
Generated By: All SCP logic.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

3181 Session is not logged on.
Explanation: This error is returned to the end user when session context for his console request cannot be located.
Generated By: ScpTask.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

3182 No utility is running. Command ignored.
Explanation: This error is returned to the end user when utility data is delivered to the console driver and no utility is
running on behalf of the session.
Generated By: ScpTask.
For Whom: End User.
Remedy: Start the appropriate utility and try the utility command again.

3183 Unrecognized command keyword: %VSTR.
Explanation: The supervisor command is not valid. The only commands supported are START and STOP.
Generated By: ScpTask.
For Whom: End User.
Remedy: Correct the syntax of the supervisor command and try again.

3184 Missing utility name. Command ignored.
Explanation: A console supervisor START command did not contain a utility name.
Generated By: ScpTask.
For Whom: End User.
Remedy: Correct the syntax of the START command and try again.

3185 Utility name is too long. Command ignored.
Explanation: A console supervisor START command contains a utility name that exceeds 11 characters.
Generated By: ScpTask.
For Whom: End User.
Remedy: Correct the syntax of the START command and try again.

3187 Utility terminated.
Explanation: The console utility that was running has exitted.
Generated By: ScpTask.
For Whom: End User.
Remedy: This error is an informational error. After this error has been received, a new utility may be started.

3188 The %VSTR command is not yet implemented.
Explanation: The supervisor command that was specified is not yet implemented.
Generated By: ScpTask.
For Whom: End User.
Remedy: Wait for a future software release that supports the command.

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