Informix Error -590: Routine cache corrupted.
Cause and resolution
Routine cache corrupted.
If this internal error recurs, note all circumstances and contact IBM Informix Technical Support.
-590 Procedure cache corrupted.
If this internal error recurs, note all circumstances and contact IBM Informix Technical Support.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-590 (also documented under the message "Procedure cache corrupted," per the official guidance) is flagged as an internal error with no documented application-level trigger — the server's in-memory cache of compiled SPL routines/stored procedures is in an unexpected state.
- A genuine internal engine condition in the routine-cache management, per the official guidance's framing, with no documented application-level cause.
- Concurrent DDL against a stored procedure (
CREATE/DROP/ALTERon a routine) happening at the same moment other sessions are executing it, as a plausible non-engine-internal contributor worth ruling out even though not explicitly named by the official text. - Memory pressure or corruption in the server's virtual-processor memory pools generally, surfacing here specifically because the routine cache happened to be the structure affected.
Solutions / Resolution
- If this recurs, note all circumstances and contact IBM Informix Technical Support, per the official guidance — there is no documented general application-level fix.
- Capture which routine(s) were being executed or modified at the time, and whether any concurrent DDL against a stored procedure was happening, since that's a plausible contributor worth documenting for escalation even though not explicitly named by the official text.
- Consider a controlled instance restart if the condition persists across sessions, since a corrupted in-memory cache would typically clear on restart — but only after capturing diagnostic detail, and coordinate with whoever administers the instance before restarting.
Examples
Capturing circumstances for escalation
-- Record which routine was executing, and any recent CREATE/DROP/ALTER
-- PROCEDURE/FUNCTION activity against it or related routines, at the
-- time -590 occurred.
Diagnostic Checks
- Check for concurrent DDL against stored procedures (
CREATE/DROP/ALTER PROCEDURE/FUNCTION) around the time of the failure. - Capture full circumstances for escalation if no concurrent DDL explains it.
Related Errors / Related Topics
No closely related error codes are cross-referenced for -590 in this set yet.
An internal routine-cache error — check for concurrent DDL against stored procedures before escalating to IBM Informix Technical Support.