Teradata SQL Error and Failure Codes from Error 2790 To 2798

SQLServerF1_Header_Small

2790 NUSI row hash code is incorrect.
Explanation: A non-unique secondary index row has an 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.

2791 Primary and fallback data row checksums do not match.
Explanation: A mismatch is detected during a checksum 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.

2792 Primary and fallback USI row checksums do not match.
Explanation: A mismatch is detected when a checksum comparison of the primary copy of a index row to its fallback
copy.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

2793 MLoad MARK DUPLICATE INSERT (dup row)
Explanation: An MLoad apply error table row with this code marks a duplicate-insert event where the newly built row
is identical to an old row in the target table.
Generated By: AMP MLoad steps
For Whom: MLoad user
Remedy: The MLoad user must decide if the duplicate row is an anomaly. The user may then use the contents of the
error table row to perform event logging or recovery actions.

2794 MLoad MARK DUPLICATE INSERT (dup key)
Explanation: An MLoad apply error table row with this code marks a duplicate-insert event where the newly built row
has the same unique primary key value as an old row in the target table.
Generated By: AMP MLoad steps
For Whom: MLoad user
Remedy: The MLoad user must decide if the duplicate row is an anomaly. The user may then use the contents of the
error table row to perform event logging or recovery actions.

2795 MLoad MARK DUPLICATE UPDATE
Explanation: An MLoad apply error table row with this code marks a duplicate-update event where the newly built row
is identical to an old row in the target table. This event will only occur if the target table has a non-unique primary index
(NUPI).
Generated By: AMP MLoad steps
For Whom: MLoad user
Remedy: The MLoad user must decide if the duplicate row is an anomaly. The user may then use the contents of the
error table row to perform event logging or recovery actions.

2796 MLoad MARK MISSING DELETE
Explanation: An MLoad apply error table row with this code marks a missing-delete event where the row specified for
delete is not found in the target table.
Generated By: AMP MLoad steps
For Whom: MLoad user
Remedy: The MLoad user must decide if the missing row is an anomaly. The user may then use the contents of the error
table row to perform event logging or recovery actions.

2797 MLoad MARK MISSING UPDATE
Explanation: An MLoad apply error table row with this code marks a missing-update event where the row specified for
update is not found in the target table.
Generated By: AMP MLoad steps
For Whom: MLoad user
Remedy: The MLoad user must decide if the missing row is an anomaly. In the case of this error, the mark rows for the
missing update operations places nulls for the target table columns in the error table. The user may still use the contents of
the error information in the error table row to perform event logging or recovery actions.

2798 MLoad: Prime Key mismatch on insert missing update.
Explanation: The user attempted to perform the insert part of a ’DO INSERT FOR MISSING UPDATE ROWS’ with a different
prime key values for the update and insert.
Generated By: AMP MLoad steps
For Whom: MLoad user
Remedy: The MLoad user must correct the job to ensure that the update and insert rows have the prime key.

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