Oninit
Talk to an expert →

Informix Error -241

-241 Cannot rollback work.

The database server cannot execute a ROLLBACK WORK statement. Check the accompanying ISAM error code for more information. A problem probably exists in accessing the transaction log.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-241 completes the BEGIN/COMMIT/ROLLBACK trio with -237 and -238: a ROLLBACK WORK statement failed, most likely due to a problem accessing the transaction log — and this one is the most serious of the three, since it means even undoing a transaction isn't currently possible.

  1. A problem accessing the transaction log, the same family as -237/-238's causes.
  2. The accompanying ISAM error code identifies exactly which specific log-access problem is occurring.
  3. Storage or hardware failure severe enough to affect both commit and rollback paths — worth treating as a serious signal if this appears rather than -238, since rollback failing too suggests a deeper problem than an isolated commit issue.
Solutions / Resolution
  1. Check the accompanying ISAM error code first, per the official guidance.
  2. Address whichever specific log-access problem is named, using that code's own guidance elsewhere in this catalogue.
  3. Treat this with elevated urgency compared to -237/-238. If a transaction can neither commit nor roll back, the session may be stuck holding locks and resources indefinitely — involve the administrator promptly rather than retrying repeatedly.
Examples
Checking the accompanying code first
-- The specific ISAM error code accompanying -241 determines the fix:
--   -120/-224: log file can't be opened — check path, permissions, existence
--   -118/-121: log file exists but has a read/write problem — check hardware, space
Diagnostic Checks
  1. Check the accompanying ISAM error code.
  2. Check transaction log file status and accessibility, per -120/-224's diagnostic steps.
  3. Check whether other sessions are similarly affected, which would suggest a systemic log/storage problem rather than something isolated to one session.
Related Errors / Related Topics
  • -237 — "Cannot begin work." The first member of the same transaction-lifecycle log-access family.
  • -238 — "Cannot commit work." The middle member of the same family — worth comparing against, since a session that can't commit or roll back is more serious than either individually.

If a session can't roll back, involve the administrator promptly — this can leave the session stuck holding resources indefinitely.