Restrictions and Limitations for Archive/Recovery and Partitioned Tables
You cannot restore or copy an archive that contains partitioned tables to an earlier release of Teradata Database that does not support row partitioning or column partitioning.
If you restore or copy a partitioned table to another system, you should revalidate the table headers on the target system after the restore or copy operation completes.
Because many of the ALTER TABLE MODIFY operations change the version number of tables, you cannot perform the following operations after modifying primary index partitioning, uniqueness, or column set members.
If Archive/Recovery encounters such physical changes to a table during a rollforward or rollback operation, the operation stops and places an error message in the output listing.
The following table definition options and table definition‑related operations performed by other statements do not invalidate future restorations of selected partitions for the targeted or referenced tables.
When the target and source are different systems, you must repeat each of the previously listed operations on the affected tables of the target system to ensure that the 2 are kept in synchrony.
See “Rules for Retaining Eligibility for Restoring or Copying Selected Partitions” on page 126 for information about modifications to a table definition that do make future restore or copy operations of selected partitions for targeted or referenced tables non‑valid.