When a check constraint table is updated, added to, or deleted by a data manipulation SQL statement, HiRDB performs checking during execution to guarantee data integrity. However, if the table is manipulated by the utilities listed in Table 13-24, data integrity may not be guaranteed because HiRDB does not perform integrity checking. If you specify USE in the pd_check_pending operand and perform these operations, the check constraint table is placed in check pending status.
Table 13-24 Operations on check constraint tables that nullify the guarantee of data integrity and the conditions under which loss of data integrity occurs
Operation on table or RDAREA | Condition for loss of data integrity | |
---|---|---|
Database load utility (pdload) | Data reload | Data that does not satisfy search conditions specified in the check constraint definition is loaded. Data that does not satisfy search conditions specified in the check constraint definition is reloaded. During operation of updatable online reorganization#, in a replica RDAREA in the current database, you used the database load utility (pdload) to perform an operation on a check constraint table of the replica RDAREA, which caused a loss of data integrity (loss of data integrity occurs after reflection processing). |
Database reorganization utility (pdrorg) | Reload (-k reld) | |
Updatable online reorganization reflection processing (pdorend) |