Teradata SQL Error and Failure Codes from Error 2744 To 2754

SQLServerF1_Header_Small

2744 Dictionary version does not match header version.
Explanation: This message is displayed if the version field in the table header does not match the corresponding version
number in the DBC.TVM record for the table.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2745 Warning: USI flagged as invalid on one or more AMPs.
Explanation: This message is displayed if any AMP does not have the valid flag set for the USI. By default, all remaining
index checks for the index are bypassed. The CHECKINVALIDSI option may be specified to continue with index checking
despite the invalid state. This might be useful in determining why the index was marked invalid.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2746 Warning: NUSI flagged as invalid on one or more AMPs.
Explanation: This message is displayed if any AMP does not have the valid flag set for the NUSI. By default, all remaining
index checks for the index are bypassed. The CHECKINVALIDSI option may be specified to continue with index checking
despite the invalid state. This might be useful in determining why the index was marked invalid.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2747 Primary and fallback data counts do not match.
Explanation: This message is displayed if the count of rows in the primary data subtable on each AMP does not match
the sum of the counts of the rows in the corresponding fallback data subtables on other AMPs in the same cluster.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2748 Data count does not match the USI count.
Explanation: This message is displayed when the sum of rows in the primary data subtables across all AMPs does not
match the sum of the rows in the corresponding primary unique secondary index subtables across all AMPs.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2749 Primary and fallback USI counts do not match
Explanation: This message is displayed when the count of rows in the primary unique secondary subtable on each AMP
does not match the sum of counts of the rows in the corresponding fallback unique secondary index subtables on other
AMPs in the same cluster.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2750 Data subtable count does not match NUSI count.
Explanation: This message is displayed when the counts of the rows in each data subtable does not match the count of
rows indexed by the corresponding index subtable.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2751 Data row out of order.
Explanation: A data row is found to be out of order when the data subtables are scanned.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2752 Data row has same row id as previous row.
Explanation: Two adjacent rows with the same row id are found when the data subtables are scanned.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2753 Primary data row is on wrong AMP.
Explanation: A row is found to be on the wrong AMP when the data subtables are scanned.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2754 Fallback data row is on wrong AMP.
Explanation: A row is found to be on the wrong AMP when the data subtables are scanned.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

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