Terminating and reloading an interrupted load operation

If a failure or interruption occurs during a load operation, you can use the load utility to terminate the operation or reload the table.

If the load utility does not even start because of a user error such as a nonexistent data file or invalid column names, the operation terminates and leaves the target table in a normal state.

When the load operation begins, the target table is placed in the Load in Progress table state. In the event of a failure, the table state will change to Load Pending. To remove the table from this state, you can issue a LOAD TERMINATE to roll back the operation or issue a LOAD REPLACE to reload the entire table.

Once you have fixed the situation that caused the load operation to fail, reissue the load command. Ensure that you specify exactly the same parameters as in the original command, so that the load utility can find the necessary temporary files.

Note: Do not delete or modify any temporary files created by the load utility.

If the load operation resulting from the following command fails,

LOAD FROM file_name OF file_type  	
SAVECOUNT n 
MESSAGES message_file  
load_method 
INTO target_tablename

you would restart it by running a LOAD TERMINATE followed by the original LOAD command::

LOAD FROM file_name OF file_type  	
SAVECOUNT n 
MESSAGES message_file  
TERMINATE
INTO target_tablename

LOAD FROM file_name OF file_type  	
SAVECOUNT n 
MESSAGES message_file  
load_method 
INTO target_tablename

Failed load limitations

The BACKUP DATABASE command might return an I/O error if the LOAD command fails on a table in SMS table space and the table is left in Load Pending state.

Table data might not appear consistent when a table is in a Load Pending state. Inconsistent table data causes the BACKUP DATABASE command to fail. The table remains inconsistent until a subsequent LOAD TERMINATE or LOAD REPLACE command is completed.

You must remove the table from the Load Pending state before backing up your database.