Informix Error -889: Internal dataskip condition, should reposition to next row and continue.

Reasons / Common Causes

-889 is flagged by the official text as an internal error related to the DATASKIP mechanism (which lets a query skip over damaged/unavailable dbspaces rather than failing outright) — the server's internal handling didn't correctly reposition to the next row as expected, with no documented application-level trigger.

1. A genuine internal engine condition in DATASKIP's row-repositioning logic, per the official guidance's framing, with no other documented application-level cause.
2. DATASKIP active against a dbspace with a genuine underlying problem, plausible given the error's specific "dataskip" framing, though not explicitly named by the sparse official text.

Solutions / Resolution

1. If this recurs, note all circumstances and contact IBM Informix Technical Support, per the official guidance — there is no documented general application-level fix.
2. Check whether SET DATASKIP was active for the session/query, given the error's specific framing, and capture that detail for escalation.
3. Check the health of the dbspace(s) DATASKIP was configured to skip, since a genuinely problematic dbspace is plausible context for this error even though not explicitly named.

Examples

Checking dbspace health

$ onstat -d
-- review chunk status for the dbspace(s) involved, since a damaged or
-- offline chunk is the typical reason DATASKIP would be in use at all

Diagnostic Checks

1. Check whether DATASKIP was active for the session/query that hit this error.
2. Check the health of the dbspace(s) involved, via onstat -d.
3. Capture full circumstances for escalation.

Related Errors / Related Topics

No closely related error codes are cross-referenced for -889 in this set yet.

An internal DATASKIP row-repositioning error — check whether DATASKIP was active and the health of the dbspace(s) it was skipping, before escalating.