What triggers an offload
An offload of an active log to an archive log can be triggered by several events.
The most common situations that trigger an offload include:
- An active log data set is full.
- Db2 starts, but an active log data set is full.
- The ARCHIVE LOG command is issued.
An offload can be also triggered by two uncommon events:
- An error occurs while writing to an active log data set. The data set is truncated before the point of failure, and the record that failed to write becomes the first record of the next data set. An offload is triggered for the truncated data set as in a normal end-of-file condition. With dual active logs, both copies are truncated so the two copies remain synchronized.
- The last unarchived active log data set becomes full. Message DSNJ110E is
issued, stating the percentage of its capacity in use; IFCID trace
record 0330 is also issued if statistics class 3 is active. If all
active logs become full, Db2 issues
the following message and stops processing until offloading occurs.
DSNJ111E - OUT OF SPACE IN ACTIVE LOG DATA SETS