Oninit
Talk to an expert →

Informix Error -23503: CM error: No such dbspace.

Cause and resolution

CM error: No such dbspace.

A request for information about a dbspace, to delete a dbspace, to either add or drop a chunk from a dbspace, or to read dbspace information during startup failed because of an invalid or unused dbspace name.

Correct the name of the dbspace and resubmit the request. Contact IBM Informix Technical Support.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-23503 fires when a CM request references an invalid or unused dbspace name — per the official guidance, for a dbspace-information query, delete, chunk add/drop, or startup read.

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

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

Diagnostic Checks
  1. Check the dbspace name against the actual configured dbspaces, and correct any typo.
Related Errors / Related Topics
  • -23504 — "CM error: dbspace already exists." The mirror-image error, on a name collision when creating rather than a name not found.
  • -23552 — "The specified dbspace (%s) does not exist." The same class of dbspace-not-found error.

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