Informix Error -248: Cannot commit savepoint.

Reasons / Common Causes

-248 is the direct sibling of -220's second, less common meaning ("Cannot begin savepoint") — an internal condition around transaction savepoint handling, detectable since Version 4.1. The official guidance frames this as something to escalate if it recurs, not something with an established self-service fix.

1. An internal engine-level condition in savepoint commit 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 in an application.

Solutions / Resolution

1. If this recurs, note all circumstances and contact IBM Informix Technical Support, per the official guidance — this is framed as an internal condition without a documented general fix.
2. Capture the exact savepoint-related operations leading up to the failure for a support case, since this level of detail is more valuable than independent troubleshooting here.

Examples

There isn't a representative application-level example to give — the official documentation's own framing 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

• -220 — "There is no FROM clause in the query. / Cannot begin savepoint." The direct sibling — its second meaning is the begin-time counterpart to this commit-time condition.
• -238 — "Cannot commit work." A different, more common commit-time failure in the same general transaction-lifecycle family.

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