Teradata SQL Error and Failure Codes from Error 2662 To 2669

SQLServerF1_Header_Small

2662 SUBSTR: string subscript out of bounds.
Explanation: This error occurs when a SUBSTR is used, and either the start position used is beyond the end of the string,
the start offset plus the specified length is greater than the string length, or the specified length is negative.
Generated By: The interpretative instruction processor.
For Whom: End User.
Notes: This can be caused by an error in the second or third argument of SUBSTR.
Remedy: Fix the DBC/SQL request and resubmit.

2663 SUBSTR: string subscript out of bounds in %TVMID.%FLDID.
Explanation: This error occurs when a SUBSTR is used, and either the start position used is beyond the end of the string
or the start offset plus the specified length is greater than the string length.
Generated By: The interpretative instruction processor.
For Whom: End User.
Notes: This can be caused by an error in the second or third argument of SUBSTR.
The TvmId and FldId can be from the source or target row.
Remedy: Fix the DBC/SQL request and resubmit.

2664 The requested aggregate operation is too complex to execute.
Explanation: This error occurs when a request requires a segment longer than 32K.
Generated By: Database software for the AMPs.
For Whom: End User.
Notes: Either the request specifies many aggregate operations or one of the fields being operated on has a potential size
of several K.
Remedy: Simplify the query or avoid use of the large field. If neither approach succeeds, contact your Support Representative.

2665 Invalid date.
Explanation: This error occurs when date arithmetic is attempted on an invalid date.
Generated By: AMP Steps.
For Whom: End User.
Notes: Dates are stored as integers in the form YYMMDD, where YY is a calendar year beginning with 1900. Values such
as 861332 are invalid as dates and may not be used where the value is to be used as a DATE data type. This error can also
occur when character strings are being converted to DATE and the character data is in the wrong format or conversion
results in an invalid value.
Remedy: Correct and resubmit the request.

2666 Invalid date supplied for %TVMID.%FLDID.
Explanation: This error occurs when an operation is attempted on an invalid date and a known data field is involved.
Generated By: AMP Steps.
For Whom: End User.
Notes: Dates are stored as integers in the form YYMMDD, where YY is a calendar year beginning with 1900. Values such
as 861332 are invalid as dates and may not be used where the value is to be used as DATE data type. This error can also
occur when character strings are being converted to DATE type and the character data is in the wrong format or conversion
results in an invalid value. This is the same error as 2665, except that Tvmid and Fldid are available.
The TvmId and FldId can be from the source or target row.
Remedy: Correct and resubmit the request.

2667 Left-over spool table found : transaction aborted.
Explanation: This error occurs if a left-over spool or headerless left-over spool is used by a transaction other than the
transaction for which it was created. The transaction attempting to use this left-over spool or headerless left-over spool is
aborted, and diagnostic information about the left-over spool or headerless left-over spool appears on the system-console
screen.
Generated By: SutBldSp, SutRespF.
For Whom: Site Support Representative
Notes: Developers researching the left-over spool or headerless left-over spool problem will be interested in the consolescreen
output produced by the logging of this error.
Remedy: Contact your Support Representative.

2668 Output row buffer size exceeded (in MoveRow).
Explanation: This error occurs if, during Fast Load, the segment size limit for the output row in MoveRow is exceeded.
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.

2669 Outrow reference to source is illegal case (in MoveRow).
Explanation: This error occurs if, say during Fast Load, the cross reference to the source in MoveRow is an unspecified
or invalid case. <<-DR118679-vg185009-01
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.

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