15.00 - Restrictions and Limitations for Archive/Recovery and Partitioned Tables - Teradata Database

Teradata Database SQL Data Definition Language Detailed Topics

prodname
Teradata Database
vrm_release
15.00
category
Programming Reference
featnum
B035-1184-015K

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.

  • 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
  • See “ALTER TABLE (Basic Table Parameters)” on page 31 and “CREATE TABLE (Table Options Clause)” on page 519 for more information about these options.

  • Specifying a partitioning expression. See “ALTER TABLE (Basic Table Parameters)” on page 31 and “CREATE TABLE (Index Definition Clause)” on page 573 for more information about this option.
  • Specifying either column‑level or table‑level CHECK constraints. See “ALTER TABLE (Basic Table Parameters)” on page 31 and “CREATE TABLE (Column Definition Clause)” on page 535 for more information about these options.
  • Collecting or dropping statistics on the table. See “COLLECT STATISTICS (Optimizer Form)” on page 175 and “DROP STATISTICS (Optimizer Form)” on page 810 for more information about collecting and dropping statistics.
  • Adding comments about the table definition. See “COMMENT (Comment Placing Form)” on page 203 for more information about adding comments about a table definition.
  • Creating or dropping a hash index on the table. See “CREATE HASH INDEX” on page 322 and “DROP HASH INDEX” on page 801 for more information about creating and dropping hash indexes.
  • Creating or dropping a join index on the table. See “CREATE JOIN INDEX” on page 340 and “DROP JOIN INDEX” on page 804 for more information about creating and dropping join indexes.
  • Creating or dropping a secondary index on the table. See “CREATE INDEX” on page 334 and “DROP INDEX” on page 802 for more information about creating and dropping secondary indexes.
  • Creating, replacing, or dropping a trigger on the table. See “CREATE TRIGGER/ REPLACE TRIGGER” on page 706 and “DROP MACRO” on page 805 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” 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.