Oninit
Talk to an expert →

Informix Error -3630

-3630 Operating system error. Cannot write into a temporary file.

PERFORM earlier created a temporary file but now cannot write into it. The most likely cause of this error is that the disk has filled up. Alternatively, another user might have deleted the temporary file after it was created.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-3630 fires when PERFORM can't write into a temporary file it created earlier — per the official guidance, the most likely cause is the disk filling up; alternatively, another user might have deleted the temporary file after it was created.

  1. The disk holding the temporary file filled up, per the official guidance — the most likely named cause.
  2. Another user deleted the temporary file after it was created, per the official guidance — the alternative named cause.
Solutions / Resolution
  1. Check available disk space on the filesystem holding the temporary file, consistent with the official guidance's identification of a full disk as the likely cause.
  2. Check whether the temporary file still exists, if disk space isn't the issue.
Examples
Checking disk space
df -h /tmp
echo $DBTEMP
Diagnostic Checks
  1. Check free disk space on /tmp or DBTEMP, and whether the temporary file was deleted by another process.
Related Errors / Related Topics
  • -3050 — "Operating system error. Cannot open a temporary file." A related temporary-file error, about failing to reopen the file rather than failing to write into it.
  • -3060 — "Operating system error. Cannot create a temporary file." A related temporary-file error, about failing to create the file in the first place rather than failing to write into an already-created one.

PERFORM can't write into a previously-created temporary file — most likely the disk is full; check /tmp/DBTEMP free space and whether the file was deleted.