Oninit
Talk to an expert →

Informix Error -245

-245 Could not position within a file via an index.

The database server encountered an error when it attempted to look up a row through an index. Check the accompanying ISAM error code for more information. The table file or the index file might have been corrupted. 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

-245 is the indexed-lookup counterpart to -243: the engine encountered an error positioning within a file specifically through an index, rather than during a general read.

  1. Table file corruption.
  2. Index file corruption — the index itself pointing at an inconsistent or invalid position.
  3. General storage-integrity causes shared with other corruption conditions in this catalogue.
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.
Examples
Following the official diagnostic order
-- 1. Check the accompanying ISAM error code and OS messages first
-- 2. If nothing specific turns up:
oncheck -cI mydb:customer
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, checking the index specifically.
Related Errors / Related Topics
  • -243 — "Could not position within a table table-name." The general-read sibling — this error is the same condition, specific to indexed lookups.
  • -105 — "ISAM error: bad ISAM file format." The general corruption sibling.

Check the index specifically with oncheck -cI — this error points at the index path rather than a general table-read issue.