Recovering from a failure resulting from total or excessive loss of log data

If a situation occurs that causes the entire log or an excessive amount of log data to be lost or destroyed, operations management needs to recover from that situation.

Symptoms

This situation is generally accompanied by messages or abend reason codes that indicate that an excessive amount of log information, or the entire log, has been lost.

Diagnosing the problem

In this situation, you need to rely on your own sources to determine what data is inconsistent as a result of the failure; Db2 cannot provide any hints of inconsistencies. For example, you might know that Db2 was dedicated to a few processes (such as utilities) during the Db2 session, and you might be able to identify the page sets that they modified. If you cannot identify the page sets that are inconsistent, you must decide whether you are willing to assume the risk that is involved in restarting Db2 under those conditions.

Resolving the problem

Operations management response:

If you decide that a restart is needed, restart Db2 without any log data by using the appropriate procedure, depending on whether the log is totally or partially (but excessively) lost.