Teradata SQL Error and Failure Codes from Error 2690 To 2700

SQLServerF1_Header_Small

2690 Zero table length in Unload.
Explanation: This error occurs only when the description of the row to be unloaded has a length of zero.
Generated By: MoveOut.
For Whom: Site support representative.
Notes: This is caused by an incorrect list of EvlReprs.
Remedy: Verify that the data definition is valid.

2691 Reference to a deleted fieldid
Explanation: The caller is attempting to find a field whose fieldid has been deleted.
Generated By: FldLocat.
For Whom: Site support representative.
Notes: This may be caused by an incorrect field 5 header.
Remedy: Contact your Support Representative.

2692 Reference to a fieldid less than the base-id.
Explanation: The caller is attempting to find a field whose fieldid is less than the base fieldid for the table.
Generated By: FldLocat.
For Whom: Site support representative.
Notes: This may be caused by an incorrect field 5 header.
Remedy: Contact your Support Representative.

2693 The fieldids in field 5 are not contiguous.
Explanation: The field descriptors in field 5 should be contiguous, they are not.
Generated By: FldLocat.
For Whom: Site support representative.
Notes: This is caused by an incorrect field 5 header.
Remedy: Contact your Support Representative.

2694 The row is incorrectly formatted.
Explanation: The row has inconsistent header information or length, or is not in the new row format.
Generated By: FldLocat.
For Whom: Site support representative.
Notes: This is caused by an incorrect field 5 header.
Remedy: Contact your Support Representative.

2696 Error in the Numeric Data Processor.
Explanation: This error is caused by problems in the numeric co-processor.
Generated By: the Numeric Operations.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2697 Release 3 to 4 conversion process not complete.
Explanation: This error is the result of attempting to run Release 4 without following the proper Release 3 to 4 conversion
process.
Generated By: SSSMain.
For Whom: Site support representative.
Notes: The system will pause in system startup when this error is detected.
Remedy: The only remedy for this error is to perform an IdLoad. Typically this IdLoad would be done at release 3 and
user data archived via the release 3 Archive and Recovery Utility would then be restored.
For further assistance, contact your Support Representative.

2698 A disk read error has occurred in primitive dump area.
Explanation: The dump area is mentioned in the event message (for example, “AMPDUMP could not be saved”). The
rest of the crash dump is saved regardless.
Generated By: DBS Startup.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2699 Inconsistent ROM pointer information in a crash dump ignored
Explanation: The crash dump being saved is mentioned in the event message (e.g., “Error saving crash dump from
AMPDUMP”). The crash dump is saved anyway, using “reasonable” defaults for saving into the crash tables.
Generated By: DBS Startup.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2700 Referential constraint violation: invalid Foreign Key value.
Explanation: The new Foreign Key value in the referencing table has no corresponding value in the referenced table.
Note, this is typically caused by an SQL Insert or Update statement on a referencing table.
Generated By: SutCK1Rw & SutCKNRw.
For Whom: End user.
Remedy: Insert the new Foreign Key value into the referenced table first and then resubmit the request.

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