Teradata SQL Error and Failure Codes from Error 2734 To 2743

2734 Data row count is less than RI count.
Explanation: This message is displayed when the number of rows in the primary data subtables across all AMPs is less
than the number of rows in the corresponding reference index subtables across all AMPs. Note, data count must be greater
than or equal to the RI count.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

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

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

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

2738 %TVMID already has Fastload running
Explanation: This error occurs if a user submits a FastLoad operation for a table that already is being loaded by another
FastLoad job.
Generated By: AMP Software.
For Whom: End User.
Notes: This error means that a user has submitted a Fastload on a table that is being loaded by another Fastload.
Remedy: Take administrative action to determine which FastLoad job should be run against the table. If necessary, delete
existing rows and reload the data.

2739 Mload did not find an insert for insert missing update rows.
Explanation: Multi Load attempted to perform an insert for a missing update row but could not find the insert statement.
This could be caused by having different table names in the update and insert parts of the statement.
Generated By: AMP Multi Load Processing.
For Whom: Multi Load user.
Notes: The User should ensure that the table names in both parts of the statement are the same.
Remedy: Correct the Multi load script and resubmit the job.

2740 One or more rows found for table not in DBC.TVM.
Explanation: If any rows are found on any AMP for tables which are not recorded in TVM.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2741 Table header not found.
Explanation: This message is displayed if one or more AMPs are missing a table header.
Generated By: CheckTable
For Whom: Site support representative
Note: This code is also used as an express request crash code on a missing DBC.NEXT table header.
Remedy: Contact your Support Representative.

2742 Extraneous subtable
Explanation: This message is displayed for each AMP on which an extraneous subtable is detected.
CheckTable formats the message text as:
Extraneous subtable nnnnn on AMP vvvvv
where
nnnnn is the decimal subtable number vvvvv is the AMP processor
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2743 Mismatch on the following table header components:
Explanation: This message if displayed when the following components of the table headers on all AMPs are different
from the table header of the AMP with the lowest physical processor number of all online AMPs. The components are:
. ExternalName . DataBaseId . AccountId . StructVersion . UtilVersion . PermJrnlTblId . Protection . UserJournal . HashedTable
. Journal . Fields in field 5 . Index descriptors

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