Save and restore considerations

A partitioned table can be saved and restored just as any other database file.

The partitions of a partitioned table are database members, and hence can be saved and restored together or individually. Consider the following items when saving and restoring partitioned tables.

• If you restore only some of the partitions of a partitioned table to a system where the partitioned table did not previously exist, the system creates the partitions that you did not restore. The created partitions that were not restored cannot have any data restored.
• If you save a table partitioned by range, then drop one or more partitions, you are able to restore the dropped partitions to the partitioned table.
• If you save a table partitioned by hash, then alter the table by dropping or adding partitions, you are not be able to restore the table that was saved to the table on the system. If, however, the table on the system is deleted, you can restore the table that was saved.

Applications using the following save and restore CL commands must be changed to use Member *ALL to process all partitions of a partitioned table:

• Restore Object (RSTOBJ)
• Save Object (SAVOBJ)
• Save Restore Object (SAVRSTOBJ)