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.
- Cluster restores
- Single AMP restores
- Permanent journal rollforwards or rollbacks
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.
- Specifying table-level options that are not related to the semantic integrity of the table, including the following.
- Fallback protection
- Journaling attributes
- Free space percentage
- Data block size
- Specifying a partitioning expression. See CREATE TABLE (Index Definition Clause) for more information about this option.
- Specifying either column-level or table-level CHECK constraints. See CREATE TABLE (Column Definition Clause) for more information about these options.
- Collecting or dropping statistics on the table. See COLLECT STATISTICS (Optimizer Form) and DROP STATISTICS (Optimizer Form) for more information about collecting and dropping statistics.
- Adding comments about the table definition. See COMMENT (Comment Placing Form) for more information about adding comments about a table definition.
- Creating or dropping a hash index on the table. See CREATE HASH INDEX and DROP HASH INDEX for more information about creating and dropping hash indexes.
- Creating or dropping a join index on the table. See CREATE JOIN INDEX and DROP JOIN INDEX for more information about creating and dropping join indexes.
- Creating or dropping a secondary index on the table. See CREATE INDEX and DROP INDEX for more information about creating and dropping secondary indexes.
- Creating, replacing, or dropping a trigger on the table. See CREATE TRIGGER/ REPLACE TRIGGER and DROP MACRO for more information about creating and dropping triggers.
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 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.