Informix Error -672

Reasons / Common Causes

-672 is flagged by the official text as an internal error in the server's execution-tree data structure (the internal representation of a statement's compiled execution plan), with no documented application-level trigger.

1. A genuine internal engine condition, per the official guidance's framing, with no documented application-level cause.
2. An unusually complex or edge-case statement stressing the execution-tree builder in a way ordinary statements don't, plausible given the "invalid data structure" framing even though not explicitly named by the 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. Try simplifying or restructuring the statement that triggered it, as a practical workaround worth attempting if an unusually complex statement was involved.
3. Capture the exact statement for escalation, since the internal execution-tree condition is unlikely to be diagnosable from the error text alone.

Examples

Capturing circumstances for escalation

-- Record the exact statement that produced -672 for escalation.

Diagnostic Checks

1. Try simplifying the statement if it's unusually complex.
2. Capture the exact failing statement for escalation if simplification doesn't help or isn't feasible.

Related Errors / Related Topics

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

An internal execution-tree error — try simplifying an unusually complex statement first, then escalate to IBM Informix Technical Support with the exact statement captured.