Oninit
Talk to an expert →

Informix Error -462

-462 File close error.

This statement reads a value from a BYTE or TEXT column into a file. The database server copied the data to the file but got an operating-system error when it closed the file. Check the accompanying ISAM error code for more information, and look for operating-system messages. Typical causes include lack of disk space and hardware errors.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-462 is the close-side counterpart of -461, specific to copying a BYTE/TEXT column's data out to a file: the data was successfully copied, but the operating system reported an error while closing the destination file — most commonly insufficient disk space (a delayed write failure surfacing at close time) or a hardware failure.

  1. Insufficient disk space — some filesystems defer write errors until the final flush at close, so a space problem can surface here even though the copy appeared to succeed.
  2. A hardware failure on the underlying storage.
  3. Filesystem-level issues specific to the close operation, distinct from whatever allowed the write itself to proceed.
Solutions / Resolution
  1. Check the accompanying ISAM error code, per the official guidance, for the specific underlying reason.
  2. Check available disk space at the destination — this is the most common cause, even though the copy itself appeared to succeed before the close failure surfaced.
  3. Check for operating-system messages around the same time for hardware-level indications.
Examples
Checking disk space after a close failure
df -h /path/to/destination/
-- confirm sufficient free space was actually available at
-- the destination, even if the copy itself appeared to
-- proceed without error
Diagnostic Checks
  1. Read the accompanying ISAM error code for the specific underlying reason.
  2. Check disk space at the destination.
  3. Check OS-level messages for hardware-level indications around the same timestamp.
Related Errors / Related Topics
  • -461 — "File open error." A related file-operation failure, at the open step rather than the close step.
  • -453 — "'loc_close()' failed." A closely related locator-close failure, in the more general loc_*()-function family rather than this specific blob-to-file copy scenario.

Check disk space first, even though the actual data copy appeared to succeed — some filesystems defer space-related write failures until the file is closed.