Teradata SQL Error and Failure Codes from Error 2594 to 2603

SQLServerF1_Header_Small

2594 One of the FastExport session has been logged off
Explanation: The host has logged off one of the FastExport session which causes the response data inaccessible. If the log off occurs during the processing of SQL Select then the Select should have been aborted. On the other hand, if the log off occurs after the completion of SQL Select then the answer set is inaccessible by any remaining FastExport sessions. In this case, however, the host is still responsible to send down an End Request to delete the answer set spool file.
Generated By: LCTExpSt
For Whom: End user
Remedy: Delete the answer set spool file if necessary and then resubmit the SQL Select.

2595 The FastExport select request has been aborted.
Explanation: The current Select request has been aborted.
Generated By: LCTExpSt
For Whom: End user
Remedy: Examine the reason of the abort, do whatever necessary to correct the problem and then resubmit the Select
request.

2596 Invalid parcel sequences in the FastExport Initiate request.
Explanation: The FastExport Initiate request from the host has an invalid parcel flavor. The request should consists of
PclFMReq/PclReq and PclResp where the request parcel should conatin two 4-byte integer indicating the desired statement
number and block number.
Generated By: LCTExpSt
For Whom: End user
Remedy: Contact your Support Representative.

2597 Table Rebuild procedures required to recover AMP.
Explanation: A disk read error was encountered while executing a recovery function. The bad data block cannot be
rebuilt with the processor on-line. The AMP which detects the error will remain offline.
Generated By: RbkCtrl.
For Whom: Operator. DBA.
Remedy: Run Table Rebuild to recover the failing table and then restart the Teradata DBS.

2598 Discrepancy between CI DBD and data block.
Explanation: Following a read of a data block, the file system discovered that the information in the header portion of
the data block itself did not match information in the Data Block Descriptor in the Cylinder Index. This could be due to an undetected I/O error on a previous write, an undetected I/O error on the current read, an undetected memory error, or a software error. The logical location of the block on disk and whether the table was a spool table or permanent table is recorded in additional text printed with this message.
Generated By: Miscellaneous file system read routines.
For Whom: Site support representative
Remedy: Contact your Support Representative

2599 One of the Foreign Key columns has a Null value.
Explanation: This is not really an error message. It is used by the DBS code to determine that the Foreign Key value has
a null value.
Generated By: SutGnIR1.
For Whom: Whoever invokes SutGnIR1.
Remedy: None.

2600 Stack overflow — expression too complicated.
Explanation: This error occurs because an expression employs too many levels of parentheses or is too complex. The
maximum stack depth is eight.
Generated By: The interpretative expression processor.
For Whom: End User.
Remedy: Resubmit the request using an expression that does not nest as many levels as the expression that caused the
error.

2601 Stack overflow calculating expression involving %TVMID.%FLDID.
Explanation: This error occurs because an expression employs too many stack push operations. The maximum stack
depth is eight. The tablename and columnname identified are those of the last fields accessed in forming the stack entries.
Generated By: The interpretative instruction processor.
For Whom: End User.
Notes: The TvmId and FldId can be from the source or target row.
Remedy: Resubmit the request using an expression that does not nest as many levels as the expression that caused the
error.

2602 Internal error — Stack Underflow.
Explanation: If this error occurs while processing pseudo code, it indicates that (a) something has caused the stack to
become empty, and that (b) some instruction expected to find some data on the stack.
Generated By: The interpretative instruction processor.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2603 Bad argument for SQRT function.
Explanation: SQRT called with negative or non-numeric argument.
Generated By: The interpretative instruction processor.
For Whom: End User.
Remedy: Change query to avoid bad call to SQRT.

Above are list of Teradata Errors or Failure Codes from Error 2594 to 2603 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 *