Informix Error -237

Reasons / Common Causes

-237 is a generic wrapper around a failed BEGIN WORK — the official text names a problem accessing the transaction log as the probable cause, tying directly into the log-access family already covered elsewhere in this catalogue.

1. A problem accessing the transaction log — the officially named probable cause, potentially any of the specific conditions covered by -118 (cannot read log record), -120 (cannot open log file), -121 (cannot write log record), or -224 (cannot open transaction log file).
2. The accompanying ISAM error code identifies exactly which specific log-access problem is occurring — this generic wrapper needs that companion code to diagnose properly.
3. The database not configured for logging at all — if BEGIN WORK is attempted against a database that never had logging enabled, see -122/-128's territory instead.

Solutions / Resolution

1. Check the accompanying ISAM error code first, per the official guidance — this is what identifies the specific underlying problem.
2. Address whichever specific log-access problem is named, using that code's own guidance elsewhere in this catalogue — a missing or corrupted log file, permissions, disk space, or logging not being enabled at all each have their own established fixes.
3. Treat this with urgency, similar to -224 — it blocks the ability to start transactions entirely, not just one operation.

Examples

Checking the accompanying code first

-- The specific ISAM error code accompanying -237 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
--   -122/-128: logging isn't enabled for this database at all — see those codes' fixes

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 the database has logging enabled at all, per -122/-128's diagnostic steps.

Related Errors / Related Topics

• -224 — "Cannot open transaction log file." A likely accompanying cause — the same underlying transaction-log-access problem.
• -122 — "ISAM error: transaction not available." Relevant if the database simply isn't configured for logging at all, rather than a log-access failure on an otherwise-logged database.

Check the accompanying ISAM error code before anything else — -237 alone only says BEGIN WORK failed, not why.