Teradata Database Message 2863 - 2863 - Analytics Database - Teradata Vantage

Message

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.