Teradata SQL Error and Failure Codes from Error 2604 To 2614

2604 Bad argument involving %TVMID.%FLDID for SQRT function.
Explanation: SQRT called with negative or non-numeric argument. The indicated field is a part of the argument.
Generated By: The interpretative instruction processor.
For Whom: End User.
Notes: The TvmId and FldId can be from the source or target row.
Remedy: Change query to avoid bad call to SQRT.

2605 Bad argument for LOG function.
Explanation: LOG called with zero, negative, or non-numeric argument.
Generated By: The interpretative instruction processor.
For Whom: End User.
Remedy: CHange query to avoid bad call to LOG.

2606 Bad argument involving %TVMID.%FLDID for LOG function.
Explanation: LOG called with a zero, negative, or non-numeric argument. The indicated field is a part of the argument.
Generated By: The interpretative instruction processor.
For Whom: End User.
Notes: The TvmId and FldId can be from the source or target row.
Remedy: Change query to avoid bad call to LOG.

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

2608 Bad argument involving %TVMID.%FLDID for LN function
Explanation: LN called with a zero, negative, or non-numeric argument. The indicated field is a part of the argument.
Generated By: The interpretative instruction processor.
For Whom: End User.
Notes: The TvmId and FldId can be from the source or target row.
Remedy: Change query to avoid bad call to LN.

2609 Internal error: improper field reference.
Explanation: This error indicates that an illegal sequence of Op Codes has been executed.
Generated By: The interpretative instruction processor.
For Whom: Site support representative.
Notes: This error occurs if there is either no output row to place the field in or no field already open.
Remedy: Contact your Support Representative.

2610 Internal error: field maintenance error
Explanation: This error indicates that an illegal sequence of Op Codes has been executed.
Generated By: The interpretative instruction processor.
For Whom: Site support representative.
Notes: This error occurs if an AppendOp is executed without a field to append to.
Remedy: Contact your Support Representative.

2611 Internal error: illegal comparison operation
Explanation: This error indicates that an illegal sequence of Op Codes has been executed.
Generated By: The interpretative instruction processor.
For Whom: Site support representative.
Notes: This error occurs if the pseudo machine is told to perform a comparison operation with mismatched types (for
example, CHAR with BYTE).
Remedy: Contact your Support Representative.

2612 Internal error: illegal opcode detected.
Explanation: This error indicates that an illegal sequence of Op Codes has been executed.
Generated By: The interpretative instruction processor.
For Whom: Site support representative.
Notes: This error occurs if pseudo code contains an Op Code that is not recognized.
Remedy: Contact your Support Representative.

2613 Internal error: illegal datatype conversion
Explanation: This error indicates that an illegal sequence of Op Codes has been executed.
Generated By: The interpretative instruction processor.
For Whom: Site support representative.
Notes: This error occurs if the pseudo machine is asked to perform an illegal type conversion during a pop operation.
Remedy: Contact your Support Representative.

2614 Precision loss during expression evaluation.
Explanation: This error indicates that an expression has produced a result that is too small to be expressed in the
requested data type.
Generated By: The interpretative instruction processor.
For Whom: End User.
Remedy: Resubmit the request after changing the type specified to accommodate the result. (For example, convert DECIMAL
to FLOAT.)

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