Informix Error -215

Reasons / Common Causes

-215 is the direct sibling of -214, at open time instead of removal: the database server can't open the operating-system file or files a table is stored in. Same general category of causes — permissions, memory, hardware — with the accompanying ISAM error code carrying the specific detail.

1. OS-level file permissions preventing the file from being opened.
2. Insufficient memory preventing the open operation from completing — a resource-exhaustion condition similar in spirit to -116/-208, specifically blocking a file open rather than a general allocation.
3. Hardware issues preventing file access.
4. The underlying file missing, moved, or renamed outside the engine's own management — similar to -120's causes for log files, applied here to table data files.
5. Filesystem or mount issues — an unavailable mount, or a filesystem-level problem preventing access.

Solutions / Resolution

1. Check the accompanying ISAM error code for the specific cause, per the official guidance.
2. Check OS-level file permissions on the table's underlying file(s).
3. Check available system memory if resource exhaustion is suspected.
4. Check hardware and filesystem health.
5. Confirm the underlying file actually exists at the expected path, and hasn't been moved or deleted externally.
6. Check mount status for the filesystem hosting the table's data.

Examples

Checking the basics

ls -la /informix/dbspace/orders.dat
-- confirm the file exists and check its permissions/ownership
mount | grep /informix/dbspace
-- confirm the filesystem is actually mounted and available
free -h
-- rule out memory exhaustion as a contributing factor

A file moved or removed externally

-- A file was inadvertently moved during unrelated maintenance
-- (a filesystem reorganization, a botched migration script)
-- The engine's catalog still expects it at the original path

Restoring the file to its expected path, or updating whatever configuration references it, resolves this — check the accompanying ISAM error code to confirm this specific explanation before assuming it.

Diagnostic Checks

1. Check the accompanying ISAM error code for the specific underlying cause.
2. Check file existence, permissions, and ownership.
3. Check available system memory.
4. Check mount status for the relevant filesystem.

Related Errors / Related Topics

• -214 — "Cannot remove file for table table-name." The direct sibling — the same general category of OS-level file-access failure, at removal time instead of open time.
• -120 — "ISAM error: cannot open log file." An analogous "cannot open" condition at a different layer (the transaction log rather than a table's data file), with a similar diagnostic approach.

Check the accompanying ISAM error code and basic file/filesystem status first — this is almost always an infrastructure issue, not a SQL or schema problem.