Informix Error -770: Bad fragment id specified.
Cause and resolution
Bad fragment 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
-770 is flagged by the official text as an internal error involving an invalid fragment identifier — for a fragmented (partitioned) table, the server's internal reference to a specific fragment doesn't resolve correctly.
- A genuine internal engine condition in fragment-identifier handling, per the official guidance's framing, with no other documented application-level cause.
- An operation against a fragmented table happening concurrently with a fragmentation-scheme change (adding/dropping/altering fragments), plausible given the "fragment id" framing, even though not explicitly named by the sparse official text.
- Catalog inconsistency around a table's fragmentation metadata, in the same general category as other internal catalog-related errors in this reference (like -620/-622).
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 whether the operation involved a table that recently had its fragmentation scheme altered, given the error's specific "fragment id" framing, and capture that detail for escalation.
- Check for concurrent DDL against the table's fragmentation at the time of the failure, if multiple sessions were active.
Examples
Capturing circumstances for escalation
-- Record the specific table involved, whether its fragmentation scheme
-- was recently altered, and the exact statement in progress, for
-- escalation.
Diagnostic Checks
- Check whether the table's fragmentation scheme was recently altered.
- Check for concurrent DDL against the table's fragmentation at 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 -770 in this set yet.
An internal fragmentation-identifier error — check for a recent or concurrent fragmentation- scheme change on the table before escalating.