Effects of interruptions and errors on the offload process
Db2 can handle some types of interruptions during the offloading process.
Db2 handles interruptions to the offloading process in the following ways:
- The STOP DB2 command does not take effect until offloading is finished.
- A Db2 failure during offload causes offload to begin again from the previous start RBA when Db2 is restarted.
- Offload handling of read I/O errors on the active log is described under Recovering from active log failures , or write I/O errors on the archive log, under Recovering from archive log failures .
- An unknown problem that causes the offload task to hang means that Db2 cannot continue processing the log. This problem might be resolved by retrying the offload, which you can do by using the option CANCEL OFFLOAD of the command ARCHIVE LOG.