Informix Error -1359: Read error on TEXT or BYTE file filename.

Reasons / Common Causes

-1359's own official page text has an internal inconsistency worth flagging directly: its title says "Read error," but its body describes an error "during output to" the temporary file (i.e. a write, the same wording as -1358) — this appears to be a discrepancy in the official source page itself, not a transcription error here. Per that body text, the underlying cause is possibly a full disk or a hardware failure.

1. A full disk, per the official guidance's body text — the first named possibility.
2. A hardware failure, per the official guidance's body text — the other named possibility.
3. Whether this is genuinely a read-side or write-side failure is unclear given the title/ body mismatch on the official page — treat both directions as plausible until confirmed otherwise for the specific server version in use.

Solutions / Resolution

1. Look for operating-system messages, per the official guidance, for more diagnostic information.
2. Check available disk space as a first, likely check, per the body text's named cause.
3. If precision matters, verify against the current server version's own documentation whether -1359 is genuinely a read-side or write-side error, given the discrepancy on this page.

Examples

N/A

No specific triggering statement is documented — this is an OS-level I/O failure on a TEXT/BYTE file, with the official page itself unclear on read vs. write direction.

Diagnostic Checks

1. Check available disk space and operating-system messages for hardware-level errors, regardless of the read/write ambiguity.

Related Errors / Related Topics

• -1357 — "Read error on temporary file filename." A related, similarly-titled read-error message for a LOCATEd temp file.
• -1358 — "Write error on TEXT or BYTE file filename." A related message with body text nearly identical to -1359's own — the likely genuine write-error counterpart.

An OS-level I/O failure on a TEXT/BYTE file — the official page's title ("Read") and body ("output"/write) disagree; check disk space and OS messages regardless of direction.