Check pending status

When the integrity of table data can no longer be guaranteed, such as when SQL code or a utility has been executed on a table for which a referential constraint or a check constraint is defined, HiRDB limits the data operations that can be performed on the referencing table or the check constraint table. The status in which data operations are limited in this way because integrity cannot be guaranteed is called check pending status. To place a referencing table or a check constraint table in check pending status in order to limit data operations, either you must specify USE in the pd_check_pending operand or you must omit specification of the pd_check_pending operand. You can remove check pending status from a table by executing the integrity check utility (pdconstck). You can also use the integrity check utility to forcibly place a table in check pending status.

If you specify NOUSE in the pd_check_pending operand, data operations are not limited even if referential integrity between tables can no longer be guaranteed. In such a case, when you execute SQL code or a utility that may cause integrity to be lost, it is advisable to use the integrity check utility to forcibly place the table in check pending status and then check its integrity.

For details about check pending status and how to check the integrity of data on which the integrity check utility has been applied, see the HiRDB Version 8 Installation and Design Guide.

Organization of this section: (1) Events that set or remove check pending status; (2) Operations that are limited for a check pending status table

(1) Events that set or remove check pending status

In addition to the integrity check utility, the following utilities, commands, and SQL code can assign or remove check pending status for a referencing table.

Specification with the constraint statement of the database load utility (pdload)
Specification with the constraint statement of the database reorganization utility (pdrorg) (reload or reorganize)
Use of the database structure modification utility (pdmod) (re-initialization of an RDAREA)
PURGE TABLE statement
ALTER TABLE (CHANGE RDAREA)

For details about these utilities and commands, see the manual HiRDB Version 8 Command Reference. For details about SQL, see the manual HiRDB Version 8 SQL Reference.

(2) Operations that are limited for a check pending status table

Table 5-1 lists the operations that cannot be performed on a table that has been placed in check pending status.

Table 5-1 Operations that cannot be performed on a check pending status table

Operation attempted on check pending status table	Result
Rebalancing utility (pdrbal)	Cannot be performed.
SELECT statement (searching a target table or searching a list created from a target table) INSERT statement (insertion of data into a target table) UPDATE statement (updating a target table) DELETE statement (deleting rows from a target table) ASSIGN LIST statement (creating a list from a target table)	Each of these operations can be performed if either of the following conditions is satisfied; these operations cannot be performed in any other case: The operation is performed on a partitioned table whose storage condition is either key range partitioning or FIX hash partitioning The RDAREA on which the operation is performed is not in check pending status
pdrorg (reorganizing)	You may not be able to perform reorganization on a partitioned table that has been reorganized with flexible hash partitioning. For details, see the section on the Database Reorganization Utility (pdrorg) in the manual HiRDB Version 8 Command Reference.

5.9 Check pending status

(1) Events that set or remove check pending status

(2) Operations that are limited for a check pending status table