Teradata SQL Error and Failure Codes from Error 2680 To 2689

SQLServerF1_Header_Small

2680 Numeric processor operand error.
Explanation: This error occurs only when the numeric co-processor sends back an operand error.
Generated By: The Numeric Processor.
For Whom: End User.
Notes: This may be caused by an attempt to load data that is not numeric.
Remedy: Verify that valid numeric data was submitted from the host computer.

2681 Fast Load not allowed: DBS had been reconfigured.
Explanation: The Teradata DBS had been reconfigured before the FAST LOAD of the table was completed.
Generated By: AMP Software.
For Whom: End User.
Notes: Partial data was FASTLOADed and the Teradata DBS was reconfigured. The data in the Teradata DBS was invalidated.
Remedy: Drop this table and its associated tables, recreate them, then resubmit the request.

2682 Precision loss during data conversion.
Explanation: The data conversion has resulted in a value that is too small to be expressed in the requested data type.
Generated By: MoveRow.
For Whom: End User.
Remedy: Resubmit the request after changing the type specified for the result. For example, convert DECIMAL to
FLOAT.

2683 Numeric overflow occurred during computation.
Explanation: The data conversion has resulted in a value that is too large to be expressed in the requested data type. (For
example, an attempt is made to store 100,000.00 as DECIMAL(5,2).)
Generated By: MoveRow.
For Whom: End User.
Remedy: Resubmit the request after changing the type specified for the result. For example, convert DECIMAL to
FLOAT.

2684 Invalid calculation: division by zero.
Explanation: This error occurs when an attempt is made to divide by zero.
Generated By: MoveRow.
For Whom: End User.
Remedy: Resubmit the request after removing the division by zero.

2685 NDP stack overflow.
Explanation: This error occurs when, in converting numeric data, MoveRow exceeds the numeric co-processor stack of 8
numbers.
Generated By: MoveRow.
For Whom: Site support representative.
Notes: This is probably caused by a software error that occurred during definition of the output row.
Remedy: Contact your Support Representative.

2686 NDP stack Underflow.
Explanation: This error occurs when MoveRow converts numeric data and the numeric co-processor stack of 8 numbers
is empty.
Generated By: MoveRow.
For Whom: Site support representative.
Notes: This is probably caused by a software error that occurred during definition of the output row.
Remedy: Contact your Support Representative.

2687 The format or data contains a bad character.
Explanation: This error occurs when the user submits a numeric-to-character conversion with an illegal format, or when,
in converting characters to numeric, either the data or the format contains a bad character.
Generated By: MoveRow.
For Whom: End User.
Remedy: Validate the format used. If it is legal, then an illegal character is present in the data being converted from character
to numeric.

2688 Numeric Processor Operand Error.
Explanation: This error occurs only when the numeric co- processor sends back an operand error.
Generated By: The Numeric Processor.
For Whom: End User.
Notes: This may be caused by an attempt to load data that is not numeric.
Remedy: Verify that valid numeric data was submitted from the host computer.

2689 Field is null for column defined as NOT NULL.
Explanation: This error occurs only when the input parcel contains a null field that is not defined as nullable.
Generated By: MoveRow.
For Whom: End User.
Notes: This is caused by an incorrect input parcel.
Remedy: Verify that valid data was submitted from the host computer.

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