Recovering from temporary resource failure

Db2 sometimes experiences a temporary problem when it accesses log data sets. In this case, you need to recover from the situation so that processing can continue as normal.

Symptoms

Db2 issues messages for the access failure for each log data set. These messages provide information that is needed to resolve the access error. For example:

DSNJ104I  ( DSNJR206 RECEIVED ERROR STATUS 00000004
           FROM DSNPCLOC FOR DSNAME=DSNC710.ARCHLOG1.A0000049

*DSNJ153E ( DSNJR006 CRITICAL LOG READ ERROR
           CONNECTION-ID = TEST0001
           CORRELATION-ID = CTHDCORID001
           LUWID = V71A.SYEC1DB2.B3943707629D=10
           REASON-CODE = 00D10345

Causes

Db2 might experience a problem when it attempts to allocate or open archive log data sets during the rollback of a long-running unit of recovery. These temporary failures can be caused by:

A temporary problem with DFHSM recall
A temporary problem with the tape subsystem
Uncataloged archive logs
Archive tape mount requests being canceled

Resolving the problem

User response: You can attempt to recover from temporary failures by issuing a positive reply (Y) to the following message:

*26 DSNJ154I  ( DSNJR126 REPLY Y TO RETRY LOG READ REQUEST, N TO ABEND

If the problem persists, quiesce other work in the system before replying N, which terminates Db2.