If a routine has been defined for a table whose partitioning storage conditions are changed, the routine is invalidated. This also includes a routine created using a trigger definition (including a trigger routine created internally by HiRDB in a referential constraint operation).

You must use ALTER ROUTINE to re-create the invalidated routine.

For details about the handling when partitioning storage conditions are changed for a referenced table, a referencing table, and a check constraint table, see 13.13.11 Handling when referential constraint and check constraint are used.

When the inner replica facility is used, you must synchronize the generation numbers of all the tables whose partitioning storage conditions are to be changed and the RDAREAs storing the related resources. If referential constraint is used, you must synchronize the generation numbers of all RDAREAs storing referencing tables and referenced tables. Note that when partitioning storage conditions are changed, data is deleted from all generations of RDAREAs.

You cannot change partitioning storage conditions while a utility that updates the database is executing (such as the database load utility or the database reorganization utility). If you change partitioning storage conditions at such a time, data that does not satisfy the partitioning storage conditions might be registered in the database.