| Previous | Next |
| ERROR_RM_CANNOT_BE_FROZEN_FOR_SNAPSHOT | ERROR_TRANSACTION_NO_SUPERIOR |
ERROR_TRANSACTION_MUST_WRITETHROUGH
This status describes a late-enlistment consistency rule. The transaction has already passed the pre-prepare phase, so a resource manager cannot safely join with an enlistment mask that permits cached transactional state. KTM requires the participant to use write-through behavior and stop relying on cached data for that transaction.
Why it matters
During two-phase coordination, prepare work is the point at which an enlisted resource manager must be able to guarantee either commit or rollback. A participant that begins after the earlier phase cannot assume it can reconstruct or defer state in the same way as a participant that joined on time.
Checks for an implementation
- Record when the resource manager attempts to enlist relative to transaction notifications.
- Review the enlistment mask and the persistence rules used for the affected resource.
- Do not interpret “write-through” as a generic request to toggle an unrelated file-system flag; it is a KTM enlistment requirement for this transaction phase.
- Where possible, enlist before pre-prepare rather than trying to attach a cached participant late.
See KTM transaction processing, CreateEnlistment, and KTM notification phases.
Looking for a different code? Search another status or error code.