Informix Error -278

Reasons / Common Causes

-278 completes the savepoint-lifecycle trio with -220's second meaning ("Cannot begin savepoint") and -248 ("Cannot commit savepoint") — an internal condition in savepoint rollback handling, with the same "escalate if it recurs" framing as its siblings.

1. An internal engine-level condition in savepoint rollback handling — not tied to a documented application-level trigger.
2. Recurrence would be the notable signal — an occasional, isolated occurrence is less concerning than a pattern tied to specific savepoint usage.

Solutions / Resolution

1. If this recurs, note all circumstances and contact IBM Informix Technical Support, per the official guidance.
2. Capture the exact savepoint-related operations leading up to the failure for a support case.

Examples

There isn't a representative application-level example to give — the official documentation treats this as an internal condition to report rather than diagnose independently.

Diagnostic Checks

1. Capture the exact sequence of savepoint operations (begin, commit, rollback) leading up to the failure.
2. Check whether this is a one-time occurrence or a recurring pattern tied to specific application savepoint usage.

Related Errors / Related Topics

• -248 — "Cannot commit savepoint." The direct sibling — the commit-time counterpart to this rollback-time condition.
• -220 — "There is no FROM clause in the query. / Cannot begin savepoint." Its second meaning is the begin-time counterpart, completing the trio with -248 and this entry.

If this recurs, prioritize capturing exact circumstances for IBM Informix Technical Support over attempting to trace it to an application-level cause.