Teradata Database Message 2913 - 2913 - Analytics Database - Teradata Vantage
Teradata® VantageCloud Lake - Analytics Database Messages
- Edition
- Lake
- Product
- Analytics Database
- Teradata Vantage
- Published
- October 2022
- Language
- English (United States)
- Last Update
- 2024-02-26
- dita:mapPath
- tzr1629746512312.ditamap
- dita:ditavalPath
- ft:empty
- dita:id
- vza1585613049811
- lifecycle
- latest
- Product Category
- Teradata® Vantage™
- Message
- A specific-AMP recovery was executed out of order.
- Explanation
- A specific-AMP rollback or rollforward was attempted on a nonfallback table with unique secondary indexes.
- Generated By
- HutRecvy
- For Whom
- User.
- Notes
- A specific-AMP rollback or rollforward of nonfallback tables with unique secondary indexes should never happen. If a rollforward then it should have been preceded by either a restore (if recovering from a hardware failure) or by an all-AMPs rollforward if recovering from some other error. Either of these actions would invalidate any unique secondary indexes on the table. If a specific-AMPs rollback is being attempted then it should have been preceded by an all-AMPs rollback.
- Remedy
- Resubmit the Utility actions in the sequence described above. Note that dropping the index will cause the structure version of the table to be changed. A rollforward or rollback is not allowed across a structure change.