Conditions that result in a heuristic rollback
The following two conditions can cause a heuristic rollback:
- The logical log fills to the point defined by the LTXEHWM configuration parameter. (See the topics about configuration parameters in the HCL OneDB™ Administrator's Reference.) The source of the long-transaction condition is a piece of work being performed on behalf of a global transaction.
- An administrator executes onmode -z session_id to stop a database server thread that is executing a piece of work being performed on behalf of a global transaction.
In either case, if the piece of work has already sent a can commit message to its coordinator, the action is considered a heuristic decision.