Informix Error -23507: CM error: Chunk already exists.
Cause and resolution
CM error: Chunk already exists.
A request to add a chunk to a coserver failed because the specified pathname and offset are already configured for an existing chunk.
To add a new chunk in addition to the existing one, either choose a different pathname for it or specify an offset beyond the end of the existing chunk within the same pathname.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-23507 fires when adding a chunk with a pathname and offset already configured for an existing chunk — per the official guidance.
- The requested pathname/offset already configured for an existing chunk, per the official guidance — the direct, only cause.
Solutions / Resolution
- Choose a different pathname, or specify an offset beyond the existing chunk's end within the same pathname, per the official guidance.
Examples
N/A
No specific triggering statement is documented beyond a pathname/offset collision.
Diagnostic Checks
- Check the requested pathname/offset against existing chunks, and adjust to avoid the collision.
Related Errors / Related Topics
- -23506 — "CM error: No such chunk." The mirror-image error, on a pathname/offset not matching any chunk rather than colliding with one.
- -23548 — "CM error: This would create two chunks with the same name and offset." A related chunk-collision error, phrased around identical name/offset specifically.
A chunk's pathname/offset was already in use by an existing chunk — choose a different pathname or offset.