Teradata SQL Error and Failure Codes from Error 2670 To 2679

SQLServerF1_Header_Small

2670 Source data kind is illegal kind (in MoveRow).
Explanation: This error occurs if, during Fast Load, the type that defines the source data in MoveRow is unspecified.
Generated By: MoveRow.
For Whom: Site support representative.
Notes: A software error may have occurred during definition of the output row.
Remedy: Contact your Support Representative.

2671 Unable to find a source constant (in MoveRow).
Explanation: This error occurs if, during Fast Load, the source constant in MoveRow cannot be found.
Generated By: MoveRow.
For Whom: Site support representative.
Notes: A software error may have occurred during definition of the output row.
Remedy: Contact your Support Representative.

2672 Output data kind is illegal kind (in MoveRow).
Explanation: This error occurs if, during Fast Load, the type that defines the output data in MoveRow is unspecified.
Generated By: MoveRow.
For Whom: Site support representative.
Notes: A software error may have occurred during definition of the output row.
Remedy: Contact your Support Representative.

2673 The source parcel length does not match data that was defined.
Explanation: This error occurs if the source parcel definition is inconsistent.
Generated By: MoveRow.
For Whom: End User.
Notes: This is probably caused by incorrect definition of the input parcel from the host computer.
Remedy: Check the definition of the input parcel.

2674 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 data type specified for the result. (For example, convert DECIMAL to
FLOAT.)

2675 Numerical 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, trying to store 100,000.00 as DECIMAL(5,2).)
Generated By: MoveRow.
For Whom: End User.
Remedy: Resubmit the request after changing the data type specified for the result. (For example, convert DECIMAL to
FLOAT.)

2676 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.

2677 NDP stack overflow.
Explanation: This error occurs when MoveRow exceeds the numeric co-processor stack of 8 numbers in converting
numeric data.
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.

2678 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.

2679 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.

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