Teradata SQL Error and Failure Codes from Error 9597 To 9607

SQLServerF1_Header_Small

9597 Select list must have at least one period column.
Explanation: If <normalize select option> is specified, at least one column in the select list must be of period data type.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9598 Invalid use of NORMALIZE clause.
Explanation: If <normalize select option> cannot be specified when WITH clause or TOP N operator also specified in
the query. Also reports the above error when recursive query specifies the <normalize select option>.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9599 Fastload is not allowed on a table when primary index is part of NORMALIZE ignore column
list.
Explanation: Fastload is not allowed on a normalized PI table when PI column is part of the ignore column list.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9600 Response buffer size is insufficient to hold records 32KB.
Explanation: This error occurs if FetchRowCount value is greater than number of rows that can be returned in a single
response buffer to the host. This occurs when the below conditions are true. 1) fetchrowcount value is greater than number
of rows that would fit in 32K and 2) user specifies a response buffer <= 32K but the actual data is > 32K.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Client application can reduce the fetchrowcount value and submit a CONTINUE request. (OR) For Host utilities
that cannot handle 64KB Row Size, they should not resend the request. (OR) For Host utilities that can handle 64KB
Row Size, enlarge the application’s response buffer size to at least the size (but no more than 64,256) returned in the Info
field of the ERROR parcel and submit a CONTINUE request containing a single RESP or KEEPRESP parcel that specifies
the new response buffer size.

9601 Response buffer size is insufficient to hold one record.
Explanation: This error occurs if FRC value is greater than minimum number of rows that can be returned in a single
response buffer to the host.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Client application can reduce the fetchrowcount value and submit a CONTINUE request. (OR) Enlarge the
application’s response buffer size to the size returned in the Info field of the ERROR parcel and submit a CONTINUE
request containing a single RESP or KEEPRESP parcel that specifies the new response buffer size.

9602 Response buffer size is insufficient to hold one record 64KB.
Explanation: This error occurs if FetchRowCount value is greater than number of rows that can be returned in a single
response buffer to the host. This occurs when the below conditions are true. 1) fetchrowcount value is greater than number of rows that would fit in
64K and 2) user specifies a response buffer <= 64K but the actual data is > 64K.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Client application can reduce the fetchrowcount value and submit a CONTINUE request. (OR) For Host utilities
that cannot handle 1MB response buffer, they should not resend the request. (OR) 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

9603 Response buffer size is insufficient to hold one record 1MB.
Explanation: This error occurs if FetchRowCount value is greater than number of rows that can be returned in a single
response buffer to the host.
This occurs when fetchrowcount value is greater than number of rows that would fit in 1MB response buffer.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Client application can reduce the fetchrowcount value and submit a CONTINUE request.

9604 The request contains invalid fetch row count value.
Explanation: This error occurs if the request contains invalid FetchRowCount value in FetchRowCount parcel. Consult
the Call-Level Interface Version 2 Manual for more information on valid request parcel sequences.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Host application should send a valid FetchRowCount value.

9605 FetchRowCount value ignored.
Explanation: This is a warning only, not an error. FetchRowCount is applicable only for the datarows, current request
did not return any datarows, so FetchRowCount value is ignored . Response buffer will accomodate as many rows as possible.
Generated By: OPT modules.
For Whom: End User.
Notes: The request is still processed despite the warning.
Remedy: This message is for information only.

9607 Not enough virtual memory to proceed with the query.
Explanation: This is a task or process level limit. In thread based model(WINDOWS, LINUX), this task may be a victim
due to high consumption of memory by other threads in the process. However, in process based model, process hits the
limit of virtual address space due to high cosumption of segments by the query.
Generated By: Dispatcher.
For Whom: End user, System Suport 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 9597 To 9607 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 *