Recovering from allocation problems with the archive log
You can recover from situations in which allocation problems occur for the archive log.
Symptoms
The following message is issued:
DSNJ103I - csect-name LOG ALLOCATION ERROR DSNAME=dsname, ERROR STATUS=eeeeiiii, SMS REASON CODE=ssssssss
z/OS® dynamic allocation provides the ERROR STATUS information. If the allocation is for offload processing, the following message is also issued:
DSNJ115I - OFFLOAD FAILED, COULD NOT ALLOCATE AN ARCHIVE DATA SET
Causes
Archive log allocation problems can occur when various Db2 operations fail; for example:
- The RECOVER utility executes and requires an archive log. If neither archive log can be found or used, recovery fails.
- The active log becomes full, and an offload is scheduled. Offload tries again the next time it is triggered. The active log does not wrap around; therefore, if no more active logs are available, the offload fails, but data is not lost.
- The input is needed for restart, which fails. If this is the situation that you are experiencing, see Recovering from BSDS or log failures during restart
Resolving the problem
Operator response: Check the allocation error code for the cause of the problem, and correct it. Ensure that drives are available, and run the recovery job again. If a DFSMSdfp ACS user-exit filter exists for an archive log data set, be careful because this can cause the Db2 subsystem to fail on a device allocation error when Db2 attempts to read the archive log data set.