Oninit
Talk to an expert →

Informix Error -243

-243 Could not position within a table table-name.

The database server cannot set the file position to a particular row within the file that represents a table. Check the accompanying ISAM error code for more information. A hardware error might have occurred, or the table or index might have been corrupted (truncated). Unless the ISAM error code or an operating-system message points to another cause, run the oncheck utility (secheck with IBM Informix SE or tbcheck with IBM Informix OnLine) to check and repair table and index.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-243 is the next step after -242 in a table read's lifecycle: the table opened successfully, but the engine couldn't set the file position to a particular row. The official text specifically names truncation — the file becoming shorter than expected — as a form of corruption behind this.

  1. A hardware error affecting positioning within the table's file.
  2. Table or index corruption, specifically truncation — the file having become shorter than the engine expects, cutting off data it needs to seek into.
  3. General corruption causes shared with other severe conditions in this catalogue — an unclean shutdown, hardware failure, or an improperly taken backup.
Solutions / Resolution
  1. Check the accompanying ISAM error code and OS-level messages first.
  2. Run oncheck (secheck for IBM Informix SE, tbcheck for IBM Informix OnLine) to check and repair the table and index, per the official guidance, unless a more specific cause is already identified.
  3. Investigate root cause — a recent crash, hardware issue, or improper backup — the same discipline as other corruption cases in this range.
Examples
Following the official diagnostic order
-- 1. Check the accompanying ISAM error code and OS messages first
-- 2. If nothing specific turns up, check and repair directly:
oncheck -cd mydb:customer
Truncation as a specific signature
$ ls -la customer.dat
-rw-r--r-- 1 informix informix 4096 Sep 20 10:00 customer.dat
-- if the catalog expects this file to be significantly larger,
-- truncation (accidental or from a failed write) is the likely cause
Diagnostic Checks
  1. Check the accompanying ISAM error code and OS-level messages.
  2. Run oncheck/secheck/tbcheck if no more specific cause is identified.
  3. Compare the file's actual size against what the catalog expects, if truncation is suspected specifically.
Related Errors / Related Topics
  • -242 — "Could not open database table table-name." The preceding step in the same table- access lifecycle — opening succeeded here, but positioning within the file failed.
  • -105 — "ISAM error: bad ISAM file format." The general corruption sibling, sharing the same root-cause investigation discipline.

Check for truncation specifically — comparing the file's actual size against what the catalog expects is a quick, direct way to confirm this particular corruption signature.