Oninit
Talk to an expert →

Informix Error -602

-602 Cannot open TEXT or BYTE value.

This statement refers to a BYTE or TEXT value, but some unexpected error prevented locating the value. Roll back the current transaction. Check the accompanying ISAM error code for more information. Possibly a hardware error or data corruption of the storage space or tblspace occurred. If the error recurs, note all circumstance, and contact IBM Informix Technical Support.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-602 fires when the server can't locate/open an existing TEXT/BYTE (simple large object) value that a statement refers to — the third stage in the same family as -600 (create) and -601 (delete), sharing -601's framing around hardware error or corruption rather than -600's typical space shortage.

  1. Hardware error or data corruption in the storage space/tblspace holding the referenced BLOB value, per the official guidance — the specific, most likely cause.
  2. An underlying ISAM-level error while locating the value, per the official guidance's pointer to checking the accompanying ISAM error code for other possibilities.
  3. A stale reference to a BLOB value that was removed or relocated by means outside normal application flow (a restore, a manual storage-space operation), leaving the reference pointing at something no longer there.
Solutions / Resolution
  1. Roll back the current transaction, per the official guidance.
  2. Check the accompanying ISAM error code, per the official guidance, for the specific underlying reason.
  3. Check for hardware errors or corruption in the storage space/tblspace, per the official guidance — the same class of cause as -601, warranting platform-level disk diagnostics or an Informix consistency-check utility against the affected dbspace.
  4. If this recurs, note all circumstances and contact IBM Informix Technical Support, per the official guidance.
Examples
Checking for storage-level problems
$ onstat -d
-- review chunk status for the blobspace/dbspace the referenced TEXT/BYTE value lives in,
-- and check OS-level disk/hardware logs for related errors
Diagnostic Checks
  1. Check the accompanying ISAM error code first, per the official guidance.
  2. Check chunk status (onstat -d) and OS-level hardware/disk logs for the storage space involved, given the official guidance's specific framing around hardware error/corruption.
Related Errors / Related Topics
  • -600 — "Cannot create TEXT or BYTE value." Same family, at the create stage.
  • -601 — "Cannot delete TEXT or BYTE value." Same family, at the delete/replace stage, sharing this error's hardware/corruption framing.

The third stage in the same three-error BLOB-operation family as -600/-601 — check for hardware/corruption issues in the storage space, same as -601.