Oninit
Talk to an expert →

Informix Error -455

-455 'loc_write()' failed.

The loc_write() function provided in the locator structure for a BYTE or TEXT value in this statement was called and returned a negative return code. When the value is located using user-supplied functions (loc_loctype contains LOCUSER), this function is part of the program and you have to diagnose its problems yourself. When the value is located in a file (loc_loctype contains LOCFILE or, in a 4GL program, the variable has been located in a file), this error indicates that the system-supplied loc_write() function was not able to write to the file. Possibly the disk is full, you do not have write permission for the disk, or a hardware error occurred.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-455 is the write-side counterpart of -454 in the same loc_*()-function family: loc_write() returned a negative code.

  1. When using a user-supplied locator function, the failure is entirely application-defined — diagnosing it is the application developer's own responsibility.
  2. When using the system-supplied function accessing a file, a full disk — the most common concrete cause for a file-based write failure.
  3. Insufficient write permissions on the target file/directory.
  4. A hardware error on the underlying storage.
Solutions / Resolution
  1. For a user-supplied locator function, add diagnostic logging inside it to determine why loc_write() is returning a negative code.
  2. For a file-based locator, check available disk space first, per the official guidance — this is the most common concrete cause.
  3. Check write permissions on the target file/directory.
  4. Check for underlying hardware/disk errors if space and permissions both check out.
Examples
Checking disk space and permissions before retrying
df -h /path/to/locator/output/
ls -ld /path/to/locator/output/
-- confirm sufficient free space and write permission for the
-- target directory
Diagnostic Checks
  1. Determine whether a user-supplied or system-supplied (file-based) loc_write() is in use.
  2. For a user-supplied function, add logging inside it to find the actual failure reason.
  3. For a file-based locator, check disk space, write permissions, and hardware health.
Related Errors / Related Topics
  • -454 — "'loc_read()' failed." The read-side counterpart in the same locator-function- failure family.
  • -452 — "'loc_open()' failed." The open-side counterpart in the same family.

Check disk space first for a file-based locator write failure — it's the most common concrete cause, per the official guidance.