Inconsistencies in a distributed environment
In a distributed environment, when a Db2 subsystem restarts, Db2 indicates its restart status and the name of its recovery log to the systems that it communicates with. The two possible conditions for restart status are warm and cold.
A cold status is associated with a cold start, which is a process by which a Db2 subsystem restarts without processing any log records. Db2 has no memory of previous connections with its partner. The general process that occurs with a cold start in a distributed environment is as follows:
- The partner (for example CICS®) accepts the cold start connection and remembers the recovery log name of the Db2 subsystem that experienced the cold start.
- If the partner has indoubt thread resolution requirements with the cold-starting Db2 subsystem, those requirements cannot be satisfied.
- The partner terminates its indoubt resolution responsibility with the cold-starting Db2 subsystem. However, as a participant, the partner has indoubt logical units of work that must be resolved manually.
- Because the Db2 subsystem has an incomplete record of resolution responsibilities, Db2 attempts to reconstruct as much resynchronization information as possible.
- Db2 displays the information that it was able to reconstruct in one or more DSNL438 or DSNL439 messages.
- Db2 then discards the synchronization information that it was able to reconstruct and removes any restrictive states that are maintained on the object.