Teradata SQL Error and Failure Codes from Error 2778 To 2789

SQLServerF1_Header_Small

2778 Primary and fallback data rows do not match.
Explanation: A mismatch is detected during a byte by byte comparison of the primary copy of a data row to its fallback
copy.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2779 USI row hash code is incorrect.
Explanation: A primary (or fallback if am AMP is down) unique secondary index row has incorrect hash code. The hash
code is not corrected in the remainder of the checking process.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2780 USI row has duplicate key.
Explanation: A primary (or fallback if an AMP is down) unique secondary index row which has the same index key as
another row in the same hash code. 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.

2781 Data row indexed by USI row with incorrect key.
Explanation: A discrepancy is detected when the key of each unique secondary index row is compared to the expected
key extracted from the data row.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2782 Primary and fallback USI rows do not match.
Explanation: A mismatch is detected during a byte by byte comparison of the primary copy of an index row to its fallback
copy.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2783 NUSI row incorrectly has continuation flag set. ***OBSOLETE***
Explanation: Inconsistencies in the setting of the index continuation flags are detected during traversal of index subtables.
The row still participates in the remainder of the check.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2784 NUSI row incorrectly has continuation flag clear.
Explanation: Inconsistencies in the setting of the index continuation flags are detected during traversal of index subtables.
The row still participates in the remainder of the check.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2785 Data row indexed by NUSI row with incorrect key.
Explanation: A discrepancy is detected when the key of the nonunique secondary index row which indexes each data
row is compared to the expected key extracted from the data row.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2786 NUSI data row ID out of order.
Explanation: Out of order indexed data rows are detected during the check for nonunique secondary indexes.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2787 Table check bypassed due to pending
Explanation: The table header on one or more AMPs has a field 4 present which indicates that the table is in the process
of being Fast Loaded, Restored or has been Recovery Aborted.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2788 Table header not found for table.
Explanation: For each table recorded in TVM which does not have a corresponding table header on one or more AMPs.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2789 Disk read error during checking process.
Explanation: A read error was encountered during CheckTable processing. The current table check is aborted and NO
automatic rebuild action is taken. An error is also logged to Event Log file system.
This error includes an indication of if the read error occurred on a spool file or a data or index subtable and the AMP on
which the error occurred.
Generated By: CheckTable
For Whom: Site support representative
Remedy: If the error occurred on a spool file, attempt to repeat the check on the table that CheckTable was processing
when the error was reported.
If the error occurred on a user table, the data may be recovered via a Table Rebuild, DROP/CREATE index or Restore as
appropriate. For additional assistance, contact your Support Representative.

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