Informix Error -23511: CM error: No such dbslice.
Cause and resolution
CM error: No such dbslice.
A request for information about a dbslice, to delete a dbslice, to identify a dbslice as the basis for a logslice, or to read dbslice information during startup failed because the referenced dbslice is not in use.
Correct the name of the dbslice and resubmit the request. If necessary, contact IBM Informix Technical Support.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-23511 fires when a dbslice-information query, delete, logslice-basis identification, or startup read references a dbslice not in use — per the official guidance.
- A dbslice name not currently in use, per the official guidance — the direct, only cause.
Solutions / Resolution
- Correct the dbslice name and resubmit the request, per the official guidance.
- Contact IBM Informix Technical Support if necessary.
Examples
N/A
No specific triggering statement is documented beyond an invalid dbslice name.
Diagnostic Checks
- Check the dbslice name against the actual configured dbslices, and correct any typo.
Related Errors / Related Topics
- -23512 — "CM error: dbslice already exists." The mirror-image error, on a name collision when creating rather than a name not found.
A CM request named a dbslice that doesn't exist — correct the name and resubmit.