Restrictions for system-period data versioning

When a table is enabled for system-period data versioning, certain restrictions apply.

• For point-in-time recovery, to keep the data in the system-period temporal table and the data in the history table synchronized, you must recover the table spaces for both tables as a set. You can recover the table spaces individually only if you specify the VERIFYSET NO option in the RECOVER utility statement.
• You cannot run a utility operation that deletes data from a system-period temporal table. These utilities include LOAD REPLACE, REORG DISCARD, and CHECK DATA DELETE YES.
• You cannot run the CHECK DATA utility on a system-period temporal table with the following options: SHRLEVEL REFERENCE, LOBERROR INVALIDATE, AUXERROR INVALIDATE, or XMLERROR INVALIDATE. When these options are specified, the CHECK DATA utility fails with return code 8 and message DSNU076I.
• You cannot alter the schema (data type, check constraint, referential constraint, etc.) of a system-period temporal table or history table; however, you can add a column to system-period temporal table.
• You cannot drop the history table or its table space.
• You cannot define a clone table on the system-period temporal table or the history table.
• You cannot create another table in table space for either the system-period temporal table or history table.
• On the history table, you cannot use the UPDATE, DELETE, or SELECT statement syntax that specifies the application period.
• You cannot rename a column or table name of a system-period temporal table or a history table.