Scenario: Correcting damage from an incorrect heuristic decision about an indoubt thread

If an incorrect heuristic decision is made regarding an indoubt thread, an organization can recover from this incorrect decision.

Symptoms

When the Db2 subsystem at SEA reconnects with the Db2 at LA, indoubt resolution occurs for LUWID=16. Both systems detect heuristic damage, and both generate alert A004; each writes an IFCID 207 trace record. Message DSNL400 is displayed at LA, and message DSNL403 is displayed at SEA.

Causes

This scenario is based on the conditions described in Scenario: Recovering from communication failure.

The LA administrator is called to make an heuristic decision and decides to abort the indoubt thread with LUWID=16. The decision is made without communicating with SEA to determine the proper action. The thread at LA is aborted, whereas the threads at SEA and SJ are committed. Processing continues at all systems. The Db2 subsystem at SEA has indoubt resolution responsibility with LA for LUWID=16.

Environment

The following figure illustrates the environment for this scenario.

Figure 1. Resolution of indoubt threads. Scenarios for resolving problems with indoubt threads contains a detailed description of the scenario depicted in this figure.
Begin figure description. This figure is a flowchart that depicts threads between four systems that are located at three different locations. End figure description.

In this scenario, processing continues. Indoubt thread resolution responsibilities have been fulfilled, and the thread completes at both SJ and LA.

Resolving the problem

Database administrator response: Correct the damage. This is not an easy task. Since the time of the heuristic action, the data at LA might have been read or written by many applications. Correcting the damage can involve reversing the effects of these applications, also. The available tools are:
  • DSN1LOGP utility, which generates a summary report that identifies the table spaces that were modified by the LUWID=16 thread.
  • The statistics trace class 4, which contains an IFCID 207 entry. This entry identifies the recovery log RBA for the LUWID=16 thread.
Notify IBM® Support about the problem.