Heuristic decisions about whether to commit or abort an indoubt thread

From the perspective of Db2, a decision to commit or roll back an indoubt unit of recovery by any means but the normal resynchronization process is a heuristic decision.

If you commit or roll back a unit of work and your decision is different than the other system's decision, data inconsistency occurs. This type of damage is called heuristic damage.

If this situation should occur, and your system then updates any data that is involved with the previous unit of work, your data is corrupted and is extremely difficult to correct.

In order to make a correct decision, you must be absolutely sure that the action you take on indoubt units of recovery is the same as the action that the coordinator takes. Validate your decision with the administrator of the other systems that are involved with the logical unit of work.