Teradata SQL Error and Failure Codes from Error 2857 To 2865

SQLServerF1_Header_Small

2857 Rollforward/Rollback: Not applicable on specified tables.
Explanation: This error occurs when a user issues a Rollforward/Rollback request to recover some data tables. The table
names specified in the statement do not have an after journal for Rollforward or before journal for Rollback.
Generated By: StpMrL.
For Whom: End User.
Notes: A Rollforward operation is applicable only if the table to be recovered has an after image journal. A Rollback operation
is applicable only if the table to be recovered has a before image journal.

2860 Operation not allowed: %DBID.%TVMID was recovery aborted.
Explanation: This error occurs only when a user issues a request for a table that was recovery aborted.
Generated By: AMP Steps.
For Whom: End User.
Notes: The table does exist, but it was recovery aborted by some authorized personnel during system recovery. The content
of this table is questionable.
Remedy: The table must be dropped and data recreated in some form (either via the Restore or FastLoad facility). The
owner of this table should be informed of the situation.

2861 Data inconsistency detected – Fallback rowid already in use
Explanation: This error is logged when an AMP attempts to insert a fallback row and the rowid is already in use.
Generated By: AMP Steps.
For Whom: DBA Site support representative
Notes: This may be the result of an operational error during recovery (Restore, Rollback or Rollforward) or the result of a
software problem.
Additional information is logged to identify the table and row in error.
This often is accompanied by a ErrAMPDataCorr error being returned in response to a user request.
Remedy: If the table has been the target of improper recovery operations, restore the table or drop and recreate it.
If the table has not been the target of improper recovery operations, contact your Support Representative.

2862 Data inconsistency detected – Fallback row not found
Explanation: This error is logged when an AMP attempts to access a fallback row in order to update or delete it and the
row is not found.
Generated By: AMP Steps.
For Whom: DBA Site support representative
Notes: This may be the result of an operational error during recovery (Restore, Rollback or Rollforward) or the result of a
software problem.
Additional information is logged to identify the table and row in error.
This often is accompanied by a ErrAMPDataCorr error being returned in response to a user request.
Remedy: If the table has been the target of improper recovery operations, restore the table or drop and recreate it.
If the table has not been the target of improper recovery operations, contact your Support Representative.

2863 Data inconsistency detected – Data row not properly indexed
Explanation: This error is logged when an AMP attempts to update or delete a row and a secondary index or reference
index entry for the row is not found.
Generated By: AMP Steps.
For Whom: DBA Site support representative
Notes: This may be the result of an operational error during recovery (Restore, Rollback or Rollforward) or the result of a
software problem.
Additional information is logged to identify the table, row and index in error.
This often is accompanied by a ErrAMPDataCorr error being returned in response to a user request.
If the error is reported against a non unique secondary index, the transaction rollback which may automatically be invoked
as a result of the error may fix the indexing of the specific row. Other rows or other indexes for the same row may still be
incorrect.
Remedy: If the table has been the target of improper recovery operations, restore the table or drop and recreate it.
If the table has not been the target of improper recovery operations, contact your Support Representative.

2864 Data inconsistency detected – Data row already indexed
Explanation: This error is logged when an AMP attempts to update or insert a row and a secondary index entry for the
row already exists.
Generated By: AMP Steps.
For Whom: DBA Site support representative
Notes: This may be the result of an operational error during recovery (Restore, Rollback or Rollforward) or the result of a
software problem.
Additional information is logged to identify the table, row and index in error.
This often is accompanied by a ErrAMPDataCorr error being returned in response to a user request.
If the error is reported against a non unique secondary index, the transaction rollback which may automatically be invoked
as a result of the error may fix the indexing of the specific row. Other rows or other indexes for the same row may still be
incorrect.
Remedy: If the table has been the target of improper recovery operations, restore the table or drop and recreate it.
If the table has not been the target of improper recovery operations, contact your Support Representative.

2865 Data corruption detected in %DBID.%TVMID.
Explanation: The current request was aborted because the Teradata DBS detected internal inconsistencies in the table.
Generated By: AMP Software.
For Whom: End User.
Notes: This may be the result of an operational error during recovery (Restore, Rollback or Rollforward) or the result of a
software problem.
Often, another error (such as ErrAMPDupFBRId, ErrAMPMissFBRow, ErrAMPRowNotIdx or ErrAMPRowIdx) is logged
on the Teradata DBS console which contains more information about the nature of the data corruption.
Remedy: If the table has been the target of improper recovery operations, restore the table or drop and recreate it.
If the table has not been the target of improper recovery operations, contact your Support Representative.

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