Informix Error -281
-281 Could not add index to a temporary table.
Check the accompanying ISAM error code to find out the specific problem, and look for operating-system error messages that might give more information. Possibly the disk is full.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-281 is the temporary-table-specific sibling of -212 — an index couldn't be added, most likely because the disk (temp space) is full.
- Insufficient space in the temp dbspace/directory — the officially named probable cause,
tying into the same
DBSPACETEMP/DBTEMPfamily as -179/-199/-221/-229. - Other ISAM-level failures during index creation, identified by the accompanying code.
Solutions / Resolution
- Check the accompanying ISAM error code and OS-level messages first.
- Check available space in the temp dbspace/directory given how directly the official text points at disk fullness.
- Address whatever the accompanying ISAM-level code names directly, using that specific error's own guidance.
Examples
Checking temp space first
onstat -d
-- confirm free space in the configured temp dbspace(s)
Diagnostic Checks
- Check the accompanying ISAM error code.
- Check disk space in the relevant temp dbspace or directory.
Related Errors / Related Topics
- -212 — "Cannot add index." The direct structural sibling — same accompanying-code pattern, for ordinary tables rather than temporary ones.
- -179 — "ISAM error: No free disk space for sort." Part of the same temp-space
configuration family (
DBSPACETEMP/DBTEMP).
Check temp space availability first — this is the officially named common cause.