Teradata Database Message 2830 - 2830 - 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
- Unique secondary index must be dropped before restoring table.
- Explanation
- During a single-AMP restore of a nonfallback table, the table header on disk indicated the existence of a unique secondary index.
- Generated By
- Host Utilities.
- For Whom
- End User.
- Notes
- Because a single-AMP restore should always be preceded by an all-AMPs restore with the single AMP down, and because the unique secondary indexes on a nonfallback table are invalidated during such a restore, this error indicates a user error. Either the index was added after the AMP came back up (modifications should never be made to the database until the AMP is restored), the single-AMP restore was not preceded by an all-AMPs restore, or the single-AMP restore was not preceded by an all-AMPs restore.
- Remedy
- The restore operation must be started over.