Teradata SQL Error and Failure Codes from Error 2767 To 2777

2767 Primary USI row is missing.
Explanation: A missing primary unique secondary index row is detected.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2768 NUSI row out of order.
Explanation: Out of order index rows are detected as the index subtables are traversed. The row is discarded from the
checking process.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2769 NUSI row has same row id as previous row.
Explanation: Duplicated index rows are detected as the index subtables are traversed. The row is discarded from the
checking process.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2770 Data row id referenced by NUSI is on wrong AMP.
Explanation: An indexed data row id is found which belongs to another AMP during the traversal of index subtables.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2771 Data row id referenced by fallback NUSI in wrong subtable.
Explanation: An indexed data row id is found which belongs to another fallback subtable during the traversal of index
subtables.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2772 NUSI row indexes non existent data row.
Explanation: A non existent indexed data row is detected when a check is made for nonunique secondary indexes.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2773 Data row not indexed by NUSI.
Explanation: An unindexed data row is detected when a check is made for nonunique secondary indexes.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2774 Data row indexed multiple times by NUSI.
Explanation: Multiple indexed data rows are detected when a check is made for nonunique secondary indexes.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2775 Data row hash code is incorrect.
Explanation: A primary (or fallback if an AMP is down) data row has incorrect hash code. The row’s hash code will not
be corrected in the remainder of the checking process.
Generated By: CheckTable
For Whom: Site support representative
Note: This code is also used internally by MultiLoad to log a row hashing anomaly to the error table during the application
phase.
Remedy: Contact your Support Representative.

2776 Data row has duplicate unique primary key.
Explanation: A primary (or fallback if an AMP is down) data row has the same primary key as another row in the same
hash code (unique primary index). The row is not ignored in the remainder of the checking process.
Generated By: CheckTable
For Whom: Site support representative
Note: This code is also used as a crash code during system startup if the DBC.TRANSLATION table contains rows with
duplicate primary keys.
Remedy: Contact your Support Representative.

2777 Data row is duplicate.
Explanation: A primary (or fallback if an AMP is down) data row is a duplicate of another row in the same hash code
(nonunique primary index). The row is not ignored in the remainder of the checking process.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

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