| Previous | Next |
| ERROR_TRANSACTIONMANAGER_NOT_FOUND | ERROR_TRANSACTIONMANAGER_RECOVERY_NAME_COLLISION |
ERROR_TRANSACTIONMANAGER_NOT_ONLINE
This status says that the Transaction Manager (TM) is not online for object creation or opening. A KTM transaction manager is backed by a log; after opening an existing TM, recovery must bring that log to a consistent state before transaction and resource-manager namespace objects can be used.
What to check first
- Confirm that the expected log stream exists and that the caller opens the intended transaction manager.
- After
OpenTransactionManagerorOpenTransactionManagerById, callRecoverTransactionManagerbefore opening dependent KTM objects. - Inspect the original log I/O failure or storage problem; write errors can cause a TM to go offline.
- Do not attempt to work around the condition by creating transaction handles against a partially recovered manager.
This is different from a transaction that has merely ended. The manager itself is unavailable for normal object operations until recovery succeeds.
See OpenTransactionManager, RecoverTransactionManager, and the KTM overview.
Looking for a different code? Search another status or error code.