Oninit
Talk to an expert →

Informix Error -224

-224 Cannot open transaction log file.

The database server cannot open the file in which transaction-log entries are made. No transactions can start until this file is repaired. (In an ANSI-compliant database, nothing can be done; in other databases, only queries can be made.) Report this problem to the database server administrator. For IBM Informix SE database servers, check the accompanying ISAM error code, and look for operating-system error messages that might give more information. A START DATABASE statement specifies the path to the log file. If the file has been deleted, you can re-create it as an empty file. If the path has changed, you can issue a new START DATABASE statement to redefine it.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-224 is closely related to -120's ISAM-level "cannot open log file" — the transaction log file a prior START DATABASE statement pointed at can't be opened. This blocks all transactions until repaired, and the operational impact depends on the database's compliance mode.

  1. The transaction log file was deleted — accidentally, or as part of cleanup/decommissioning without realizing the database still references it.
  2. The log file's path changed — a migration or storage reorganization — without reissuing START DATABASE to reflect the new location.
  3. Permission issues preventing the file from being opened despite existing.
  4. The underlying storage or mount became unavailable, the same general causes as -120.
Solutions / Resolution
  1. Report the problem to the database server administrator immediately — per the official guidance, this blocks all transactions until fixed, so it needs prompt attention.
  2. If the file was deleted, re-create it as an empty file.
  3. If the path changed, issue a new START DATABASE statement to redefine the log file's location.
  4. For IBM Informix SE, check the accompanying ISAM error code and OS-level messages for the specific cause — permissions, a missing file, or a mount issue.
  5. Understand the severity difference by database mode: in an ANSI-compliant database, nothing can proceed until this is fixed; in other databases, queries can still run, but no transactions can start. Communicate this distinction to anyone affected while the fix is in progress.
Examples
Recreating a deleted log file
touch /informix/logs/mydb.log
chown informix:informix /informix/logs/mydb.log
Redefining the path after a move
START DATABASE mydb WITH LOG IN '/informix/newlogs/mydb.log';
Diagnostic Checks
  1. Confirm the log file's expected path (from the last successful START DATABASE) and check its existence and permissions.
  2. Check the accompanying ISAM error code for IBM Informix SE.
  3. Determine whether the database is ANSI-compliant to understand the current operational impact while the fix is in progress.
Related Errors / Related Topics
  • -120 — "ISAM error: cannot open log file." The closest sibling — essentially the same underlying condition, reported at the ISAM layer rather than this SQL-level wrapper.

This blocks all transactions until fixed — treat it with urgency and involve the administrator immediately rather than investigating at leisure.