Oninit
Talk to an expert →

Informix Error -23527: CM error: No such logslice.

Cause and resolution

CM error: No such logslice.

A request for information about a logslice, to delete a logslice, or to read logslice information during startup failed because an invalid or unused logslice name was specified.

Correct the name of the logslice and resubmit the request. If necessary, contact IBM Informix Technical Support.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-23527 fires when a logslice-information query, delete, or startup read specifies an invalid or unused logslice name — per the official guidance.

  1. An invalid or unused logslice name, per the official guidance — the direct, only cause.
Solutions / Resolution
  1. Correct the logslice name and resubmit the request, per the official guidance.
  2. Contact IBM Informix Technical Support if necessary.
Examples
N/A

No specific triggering statement is documented beyond an invalid logslice name.

Diagnostic Checks
  1. Check the logslice name against the actual configured logslices, and correct any typo.
Related Errors / Related Topics
  • -23528 — "CM error: Logslice already exists." The mirror-image error, on a name collision when creating rather than a name not found.

A CM request named a logslice that doesn't exist — correct the name and resubmit.