Saving physical files that are temporal

Physical files that contain ROW BEGIN, ROW END, TRANSACTION START ID fields become temporal physical files when you perform an ALTER TABLE ADD VERSIONING against the system-period temporal table and specify its associated history table. A temporal file and its associated history table are in the same relationship network. If possible, save all the files in a relationship network in a single save operation.

If you restore files that are in a relationship network during separate restore operations, the system must verify that the relationships are still valid and current before implicit versioning is allowed. A CPD32FE warning is signaled when you restore files that are in the same relationship network separately. You can avoid this warning and improve restore performance if you save and restore relationship networks in a single operation.