Informix Error -21617: Temporary text file could not be opened for read/write.
Cause and resolution
Temporary text file could not be opened for read/write.
If this internal error recurs, note all circumstances and contact IBM Informix Technical Support.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-21617 is an internal mkmessage error — per the official guidance, no user-actionable
cause is documented beyond the temporary text file failing to open for read/write.
- The temporary text file failing to open for read/write, per the official guidance — no further named detail; check the file's existence and permissions.
Solutions / Resolution
- If this internal error recurs, note all circumstances and contact IBM Informix Technical Support, per the official guidance.
Examples
N/A
No specific triggering statement is documented — this is reported as an internal error.
Diagnostic Checks
- Check the temporary text file's existence and read/write permissions, and escalate to IBM Informix Technical Support if the error recurs.
Related Errors / Related Topics
- -21606 — "Error reading from temporary text file." A related temporary-file error, on reading from an already-open file rather than opening it.
- -21616 — "Temporary text file could not be created." A related temporary-file error, on creating the file rather than opening an already-created one.
mkmessage couldn't open its temporary text file for read/write — check its existence
and permissions.