Informix Error -822: Statements are already saved.
Cause and resolution
Statements are already saved.
The current SQL statement has already been saved under the name that is shown at the top of the screen. (This message does not appear to occur any longer.)
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-822 fires when a Save is attempted on the current SQL statement, but it's already saved under the name shown at the top of the screen — per the official guidance, this message is noted as no longer occurring on current versions, so it's documented here primarily for historical/older- platform reference.
- A redundant Save attempted on a statement already saved under its current name, per the official guidance — the condition this message described on platforms where it applied.
Solutions / Resolution
- No action is needed if the statement is already saved as intended — per the official guidance's framing, this reflects a redundant save attempt, not a failure requiring a fix.
- On a current server version, this message isn't expected to occur at all, per the official guidance's own note — if encountered unexpectedly, that's itself worth documenting when escalating, since it contradicts the documented current behavior.
Examples
N/A
This is a redundant-action notice rather than a fault requiring a worked example.
Diagnostic Checks
- Confirm the statement is genuinely already saved under the intended name, per the official guidance's description of the condition.
Related Errors / Related Topics
No closely related error codes are cross-referenced for -822 in this set yet.
Per the official guidance's own note, this message isn't expected on current versions — a redundant-save notice on the platforms where it applied.