Recovery from errors related to data redistribution
Recovery from failures and errors that occur during data redistribution generally requires that you consult the redistribution event log file. The log file contains useful information about data redistribution processing, including information about which table or tables, if any, failed to be processed successfully.
- A documented prerequisite for successful data redistribution was not met.
- A documented restriction on data redistribution was encountered that resulted in the interruption of the data redistribution.
- During data redistribution a table to be processed was encountered in a restricted access state, such as LOAD PENDING.
- Any other problem documented in the event log.
- CONTINUE
- This option indicates that the redistribution operation should continue until all tables specified in the original REDISTRIBUTE DATABASE PARTITION GROUP command are redistributed.
- ABORT
- This option indicates that the redistribution operation should be aborted and that all tables that have been redistributed, or partially redistributed, so far should be returned to the state they were in before the REDISTRIBUTE DATABASE PARTITION GROUP command was first run on the database partition group.
These options cannot be specified unless a previous data redistribution operation failed or completed without redistributing all tables in the database partition group. The latter case can occur if the TABLE command parameter is used and only a subset of tables is specified. In these cases, the value of the REDISTRIBUTE_PMAP_ID column in the SYSCAT.DBPARTITIONGROUPS table will have a value different from -1.
If an interface other than the REDISTRIBUTE DATABASE PARTITION GROUP command was used, continuation or abortion of data redistribution is possible by redistributing data again using the appropriate parameter value for the specified interface. See the reference information for the interface for the correct parameter values.