Scenario: What happens when the wrong Db2 subsystem is cold started

When one Db2 subsystem, instead of another Db2 subsystem, is cold started, threads are left indoubt. An organization that faces this situation can recover.

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.

If the Db2 subsystem at SJ is cold started instead of the Db2 at SEA, the LA Db2 subsystem has the LUWID=15 2 thread indoubt. The administrator can see that this thread did not originate at SJ, but that it did originate at SEA. To determine the commit or abort action, the LA administrator requests that DISPLAY THREAD TYPE(INDOUBT) be issued at the SEA Db2 subsystem, specifying LUWID=15. IMS does not have any indoubt status for this thread because it completes the two-phase commit process with the SEA Db2 subsystem.

The Db2 subsystem at SEA tells the application that the commit succeeded.

When a participant cold starts, a Db2 coordinator continues to include in the display of information about indoubt threads all committed threads where the cold starting participant was believed to be indoubt. These entries must be explicitly purged by issuing the RESET INDOUBT command. If a participant has an indoubt thread that cannot be resolved because of coordinator cold start, the administrator can request a display of indoubt threads at the Db2 coordinator to determine the correct action.