Since regular logging is not performed, the load utility uses pending states to preserve database consistency. These states can be checked by using the LIST TABLESPACES command (see the Command Reference).
The load and build phases of the load process place any associated table spaces into load pending state. To remove the load pending state (if the load operation has failed, or was interrupted), do one of the following:
The delete phase places any associated table spaces into delete pending state. This can occur when the load operation fails or is interrupted during the delete phase (removing unique key violations). Because the deletions are logged, failures can occur when log space runs out. The same actions taken to remove the load pending state can be used to remove the delete pending state.
Table spaces are placed in backup pending state if the load process completes, and:
The fourth possible state associated with the load process (check pending state) pertains to referential and check constraints, DATALINKS constraints, AST constraints, or generated column constraints. For example, if an existing table is a parent table containing a primary key referenced by a foreign key in a dependent table, replacing data in the parent table places the dependent table (not the table space) in check pending state. To validate a table for referential integrity and check constraints, issue the SET INTEGRITY statement after the load process completes, if the table has been left in check pending state. For more information about the check pending state, see Checking for Constraints Violations.