Changes Allowed to a PPI Table - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-01
dita:mapPath
utr1488824663491.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

The following changes can be made to a PPI table without affecting or preventing the restoration of data from an archive of selected partitions:

  • Table-level options that are unrelated to semantic integrity, such as FALLBACK protection, journaling attributes, free space percentage, block size, and others.
  • Use of the MODIFY PRIMARY INDEX option, which changes the partitioning expression.
  • Changes to table-level CHECK CONSTRAINTS.
  • Changes that add, drop, or modify a CHECK CONSTRAINT on a column.
  • Secondary indexes may be added or dropped.

Other changes to a PPI table are more significant in that they affect the DBC.TVM.UtilVersion. Do not restore archives of selected partitions if the archive UtilVersion does not match the table UtilVersion. DBC.TVM.UtilVersion is initially set to 1. ALTER TABLE increases the value of DBC.TVM.UtilVersion to match the table DBC.TVM.Version whenever the following significant changes occur to the referential integrity of a child table:

  • Modification of the columns of a primary index
  • Addition or deletion of columns
  • Modification of the definition of an existing column
  • Addition, deletion, or modification of the referential integrity among tables

When DBC.TVM.UtilVersion is updated for a table, previous archives are invalid for future restores or copies of selected partitions to that table, but a full table restore or copy is still valid. For more information, see the Data Dictionary (B035-1092).