Archiving and Restoring Column-Partitioned Tables and Databases
Users can archive, restore, and copy column-partitioned tables and join indexes and databases containing those tables and join indexes.
Restoring or Copying a Column-Partitioned Primary AMP Index Table
A nonempty column-partitioned primary AMP index table is invalid when restored or copied if the target system has the following differences from the source system:
To make the table valid when the number of AMPS differ, modify the table to have no primary index or drop the column-partitioned primary AMP index table.
If the target system has a different configuration or if the hash bucket size changes, ARC restores or copies a nonempty table with a primary AMP index but marks the table as invalid. In these circumstances, perform an INSERT-SELECT into a new column-partitioned table with a primary AMP index; then drop the invalid table. Alternatively, alter the table to have no primary index.
Restoring or Copying a Column-Partitioned Primary Index Table
If a column-partitioned primary index table is restored/copied to system with a different number of AMPs than the source system or if the hash bucket size changes, ARC redistributes the physical rows based on the hash maps of the target system.
A nonempty column-partitioned primary index table is invalid if it is restored or copied and the target system hash function changes. In these circumstances, perform an INSERT-SELECT into a new column-partitioned primary index table; then drop the invalid table.
ARC does not permit the archive, restore, or copy of selected partitions of a column-partitioned table or join index.