DSNI007I csect-name UNABLE TO START/RECOVER BECAUSE UNABLE TO DIRECT READ A LOG RECORD LOGRBA logrba

Explanation

Unable to START (or RECOVER) because the necessary log records could not be accessed. Either an error occurred while attempting to allocate or open the log data set or an expected log record was not found on the log.

If the message is in response to a START command, issue the -DISPLAY command to determine which resource(s) was not started. If the message is in response to a RECOVER utility, the resource is the table space or index space that is the object of the RECOVER.

LOGRBA gives the log RBA of the log record that is unavailable.

System action

The resource is not started (or recovered) and remains in the current state. If this is a START command, the resources are processed normally if there are other databases or spaces to be started and they do not involve reading the log.

System programmer response

Run the print log map (DSNJU004) utility. This may be run with Db2 up or down. Find the data set that contains the requested RBA in the output of DSNJU004. If the required RBA is not in a listed data set, one of the following may have occurred:
  • The data set was deleted from the bootstrap data set by a run of the change log inventory (DSNJU003) utility. In this case, rerun the utility to insert the missing data set name. Db2 must be down to run this utility.
  • The bootstrap data set has been damaged. In this case, the BSDS must be restored from the dump that occurred with the most recent archive log data set. DSNJU003 must be run to supply changes that occurred during and after the last offload operation. Changes may be determined from the operator's console listing.

If a listed log data set contains the required RBA, this message will be preceded by one or more error messages from the log manager (DSNJ). See these messages for appropriate action.

User response

Resubmit the utility, or reissue the START command, when the problem with the log has been resolved.

Problem determination

Issue the -DISPLAY command to verify what got started.