During database operations, SESAM/SQL carries out plausibility checks to make sure that only those changes are made to the data that are compatible with the integrity constraints.
Utility statement CHECK CONSTRAINTS
The database administrator can verify compliance with integrity constraints with the utility statement CHECK CONSTRAINTS.
The following can be checked with CHECK CONSTRAINTS:
selected integrity constraints
all integrity constraints defined in one or more base tables
all integrity constraints defined for the base tables of one or more user spaces
The database administrator can opt to check the integrity constraints for all specified tables, or just for tables in the “check pending” state (see section “Space state after the execution of utility statements”).
Integrity constraints always need to be checked with CHECK CONSTRAINTS if the data has changed after the following utility statements:
LOAD, if LOAD was executed without the CONSTRAINT CHECK clause.
RECOVER, if the current status of the database was not recovered.
In these cases, SESAM/SQL places the tables affected by the respective utility statement or the user space processed in the “check pending” state.
Information on how to deal with tables that remain in the “check pending” state after execution of the utility statement CHECK CONSTRAINTS is provided under “Using SQL statements to work with tables in a “check pending” state”.