Informix Error -771
Cause and resolution
Bad table lock id specified.
If you cannot find a direct cause for this internal error, note all circumstances and contact IBM Informix Technical Support.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-771 is flagged by the official text as an internal error involving an invalid table-lock identifier, with no documented application-level trigger.
- A genuine internal engine condition in lock-identifier handling, per the official guidance's framing, with no other documented application-level cause.
- A lock-table condition interacting with an unusual concurrency pattern, plausible in general terms given the "table lock id" framing, though the official text doesn't name specifics.
Solutions / Resolution
- If you cannot find a direct cause, note all circumstances and contact IBM Informix Technical Support, per the official guidance — there is no documented general application-level fix.
- Check lock-table health around the time of the failure:
onstat -k - Capture the exact statement/operation and concurrent activity at the time of the failure, for escalation.
Examples
Checking lock-table state
$ onstat -k
-- review active locks around the time of the failure
Diagnostic Checks
- Check
onstat -kfor lock-table state around the time of the failure. - Capture the exact statement/operation in progress for escalation.
Related Errors / Related Topics
No closely related error codes are cross-referenced for -771 in this set yet.
An internal lock-identifier error — check lock-table state (onstat -k) and capture
circumstances for escalation to IBM Informix Technical Support.