Informix Error -12143: Smart Large Objects: Invalid chunk number.
Cause and resolution
Smart Large Objects: Invalid chunk number.
The chunk number in an LO handle is not valid. Either it is out of range, or it does not exist. Most likely the LO handle is corrupt. If you are getting this error in an ESQL program, make sure that the LO handle is valid. In addition, ensure that you did not force drop the chunk.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-12143 fires when an LO handle's chunk number is invalid — per the official guidance.
- The chunk number being out of range or nonexistent, per the official guidance — most likely because the LO handle is corrupt.
- The chunk having been force-dropped, per the official guidance — a further named case for ESQL programs specifically.
Solutions / Resolution
- Make sure the LO handle is valid, per the official guidance, in ESQL programs.
- Ensure the chunk wasn't force-dropped, per the official guidance.
Examples
N/A
No specific triggering statement is documented beyond a corrupt LO handle or force-dropped chunk.
Diagnostic Checks
- Check the LO handle's validity, and check whether the chunk it references was force-dropped.
Related Errors / Related Topics
- -12142 — "Smart Large Objects: Invalid sbspace number." The same class of invalid- identifier error, for an sbspace number rather than a chunk number.
The LO handle's chunk number was invalid, likely due to a corrupt handle or a force-dropped chunk — check both.