Informix Error -12118: Smart Large Objects: Bad LO extent map.
Cause and resolution
Smart Large Objects: Bad LO extent map.
The extent map record for the smart large object is corrupt. Most likely the sbspace is corrupt. Run oncheck -ce on the sbspace. You might need to restore the sbspace from an archive.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-12118 fires when a smart large object's extent-map record is corrupt — per the official guidance.
- The sbspace most likely being corrupt, per the official guidance — the direct, named cause.
Solutions / Resolution
- Run
oncheck -ceon the sbspace, per the official guidance. - Restore the sbspace from an archive if needed, per the official guidance.
Examples
Checking sbspace extent consistency
$ oncheck -ce sbspace_name
Diagnostic Checks
- Run
oncheck -ceon the affected sbspace, and restore from archive if corruption is confirmed.
Related Errors / Related Topics
- -12060 — "Smart Large Objects: Cannot read SB_LOMAP_SLOT." A related extent-map error, on failing to read the slot rather than finding it corrupt.
- -12104 — "Smart Large Objects: Inconsistent LO map was encountered." A related extent-map error, on a detected inconsistency rather than outright corruption.
A smart large object's extent-map record is corrupt, most likely due to sbspace corruption —
run oncheck -ce and restore from archive if needed.