Recovering from unresolvable BSDS or log data set problem during restart
During a restart of Db2, serious problems with the bootstrap data set (BSDS) or log data sets might occur. However, operations management can recover from these problems. Use of dual logging (active logs, archive logs, and bootstrap data sets) can reduce your efforts in resolving these sorts of problems.
Symptoms
The following messages are issued:
- DSNJ100I
- DSNJ107I
- DSNJ119I
Causes
Any of the following problems might cause problems with the BSDS or log data sets during restart:
- A log data set is physically damaged.
- Both copies of a log data set are physically damaged in the case of dual logging mode.
- A log data set is lost.
- An archive log volume was reused even though it was still needed.
- A log data set contains records that are not recognized by Db2 because they are logically broken.
Environment
Db2 cannot be started until this procedure is performed.Resolving the problem
Operations management response:
Serious cases such as this sometimes necessitate
a fallback to a prior shutdown level.
- If you decide to fall
back (because the amount of lost information
is not excessive):
- See Preparing to recover to a prior point of consistency.
- Follow the procedure in Falling back to a prior shutdown point.
- If you decide not to fall back (because too much log information has been lost), use the alternative approach that is described in Recovering from a failure resulting from total or excessive loss of log data.