Recovering from Db2 database failure

If a Db2 failure occurs because of an allocation or open problem, you can recover from this situation.

Symptoms

The symptoms vary based on whether the failure was an allocation or an open problem:

Allocation problem

The following message indicates an allocation problem:

DSNB207I - DYNAMIC ALLOCATION OF DATA SET FAILED. 
           REASON=rrrr DSNAME=dsn

The rrrr is a z/OS® dynamic allocation reason code.

Open problem

The following messages indicate an open problem:

IEC161I  rc[(sfi)] - ccc, iii, sss, ddn,
       ddd, ser, xxx, dsn, cat

DSNB204I - OPEN OF DATA SET FAILED. DSNAME = dsn

In the IEC161I message:

rc: Is a return code.
sfi: Is subfunction information, which is displayed only with certain return codes.
ccc: Is a function code.
iii: Is a job name.
sss: Is a step name.
ddn: Is a DD name.
ddd: Is a device number (if the error is related to a specific device).
ser: Is a volume serial number (if the error is related to a specific volume).
xxx: Is a VSAM cluster name.
dsn: Is a data set name.
cat: Is a catalog name.

When this type of problem occurs:

The table space is automatically stopped.
Programs receive a -904 SQLCODE (SQLSTATE '57011').
If the problem occurs during restart, the table space is marked for deferred restart, and restart continues. The changes are applied later when the table space is started.

Operator response: