Informix Error -271

Reasons / Common Causes

-271 is a broad generic wrapper — the official text itself says this has many possible causes, and the accompanying ISAM error code is what actually identifies which one applies.

1. A locked table — the lock-conflict family (-107, -113, -134, -143, -144, -154), the same as -233.
2. A full disk — the space-exhaustion family (-131, -136, -199).
3. A duplicate key — (-100, -239, -268), if a unique constraint is involved.
4. Any other underlying ISAM-level condition the accompanying code names.

Solutions / Resolution

1. Check the accompanying ISAM error code first — this generic wrapper genuinely could mean almost anything, and the companion code is the only way to know which specific guidance elsewhere in this catalogue applies.
2. Address whichever specific cause is named, following that code's own established fix.

Examples

Checking the accompanying code first

-- The specific ISAM error code accompanying -271 determines the fix:
--   -107/-113/-134/-143/-144/-154: a lock conflict — see -233
--   -131/-136/-199: disk space exhaustion
--   -100/-239/-268: a duplicate key

Diagnostic Checks

1. Check the accompanying ISAM error code for the specific underlying cause — this is the entire diagnostic task for this error.

Related Errors / Related Topics

• -233 — "Cannot read record that is locked by another user." The closest lock-conflict wrapper sibling.
• -212 — "Cannot add index." Another "many possible causes, check the accompanying code" generic wrapper, for index creation rather than row insertion.

This error has no useful information on its own — go straight to the accompanying ISAM error code.