Teradata SQL Error and Failure Codes from Error 2799 To 2808

2799 MLoad MARK MISSING UPDATE INSERT
Explanation: An MLoad apply error table row with this code marks a missing-update insert event where the row specified
for update is not found in the target table and is subsequently inserted into 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.

2800 Aborted due to invalidated secondary index on %DBID.%TVMID.
Explanation: The table being accessed has a unique or nonunique secondary index that was invalidated as a result of
one of the below operations.
A restore operation with an AMP down or
A rollforward operation with ’primary data’ option or
A restore operation with ’no build’ option.
A corruption detected during NUSI maintenance could also end up invalidating the index. * DR126850-SG210037-01 *
No updates or inserts are allowed on this table until the index is built through a ’build’ statement of arcmain or dropped.
Generated By: AMP Steps.
For Whom: End User.
Remedy: In case of AMP down, drop the invalidated secondary indexes on the table else A ’build’ statement of arcmain
should follow to build the invalidated secondary indexes. No NUSI index access is allowed, the invalidated index needs to
be dropped and re-created. *DR126850-SG210037-01*

2801 Duplicate unique prime key error in %DBID.%TVMID.
Explanation: The request generated a row whose prime key duplicated that of an existing row in a table with a unique
prime key.
Generated By: AMP Steps.
For Whom: End User.
Remedy: Correct and resubmit the request.

2802 Duplicate row error in %DBID.%TVMID.
Explanation: An update or insert request generated a row that was a duplicate of an existing row.
Generated By: AMP Steps.
For Whom: End User.
Remedy: Correct and resubmit the request.

2803 Secondary index uniqueness violation in %DBID.%TVMID.
Explanation: A row generated by the request violated the uniqueness criteria of some unique secondary index. The
unique secondary index was created with a CREATE UNIQUE INDEX statement, or a UNIQUE constraint, or a PRIMARY
KEY specification.
Generated By: AMP Steps.
For Whom: End User.
Remedy: Correct and resubmit the request.

2804 Incompatible version in recovery status row.
Explanation: The version number in the recovery status row on disk is incompatible with the current software version.
Generated By: Recovery, Booter, Idllink or AFUINQDI.
For Whom: End User.
Notes: This error occurs in two different cases:
1) An attempt was made to migrate across more software versions than supported. This may occur as a result of setting the
version back to an obsolete version or by skipping forward across more than one software release.
2) An attempt was made to run with more than two joined DSUs with Release 3.0 versions of the Booter, or Idllink, or DBS
software.
Remedy: 1) Reboot system at correct version or contact your Support Representative.
2) Unjoin all DSUs beyond the 2nd before running with Release 3.0 software.

2805 Maximum row length exceeded in %TVMID.
Explanation: A row generated by the request exceeded the maximum row length allowed by the Teradata DBS.
Generated By: AMP Steps.
For Whom: End User.
Notes: A data row or an index row may be too long. If an index row is too long, the associated data row is very close to
the maximum limit, and/or contains compressed fields that are not stored in compressed form in index rows.
Remedy: Correct and resubmit the request.

2807 Internal error: Invalid message source.
Explanation: A message was received from an external (internal) source when it should have been from an internal
(external) source.
Generated By: AMP worker tasks.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2808 Internal error: a received message was of invalid type
Explanation: A message was received that was of an unexpected type (Response, Simplex, or Initiating).
Generated By: AMP worker tasks.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

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