Recovering from a write I/O error on an active log data set

You can recover from a situation in which a write error occurs on an active log data set.

Symptoms

The following message is issued: 

DSNJ105I - csect-name LOG WRITE ERROR DSNAME=..., LOGRBA=...,
            ERROR STATUS= ccccffss

Causes

Although this problem can be caused by several problems, one possible cause is a CATUPDT failure.

Environment

When a write error occurs on an active log data set, the following characteristics apply:

  • Db2 marks the failing Db2 log data set TRUNCATED in the BSDS.
  • Db2 goes on to the next available data set.
  • If dual active logging is used, Db2 truncates the other copy at the same point.
  • The data in the truncated data set is offloaded later, as usual.
  • The data set is not stopped; it is reused on the next cycle. However, if a DSNJ104 message indicates a CATUPDT failure, the data set is marked STOPPED.

Resolving the problem

System programmer response: If the DSNJ104 message indicates a CATUPDT failure, use access method services and the change log inventory utility (DSNJU003) to add a replacement data set. In this case, you need to stop Db2. The timing of when you should take this action depends on how widespread the problem is.
  • If the additional problem is localized and does not affect your ability to recover from any other problems, you can wait until the earliest convenient time.
  • If the problem is widespread (perhaps affecting an entire set of active log data sets), stop Db2 after the next offload.