| Previous | Next |
| MSG_CI_MASTER_MERGE_COMPLETED | MSG_CI_MASTER_MERGE_RESTARTED |
MSG_CI_MASTER_MERGE_ABORTED
MSG_CI_MASTER_MERGE_ABORTED records a merge pause caused by another error supplied in the event parameters. The embedded error is essential: the same high-level event can result from storage, resource, or catalog-state problems.
Preserve the nested error and follow the reschedule lifecycle
- Capture the substituted error code from the event instead of logging only the message constant.
- Check for a later
MSG_CI_MASTER_MERGE_RESTARTEDor a cannot-restart event for the same catalog. - Compare repeated aborts with free disk space, I/O errors, and catalog consistency events.
Master-merge documentation describes checkpointing specifically to limit how much work must be redone when a merge is paused and restarted. That makes the restart chronology diagnostically important. One abort followed by a successful restart is different from a loop that repeatedly returns to the same checkpoint. Do not immediately delete the catalog before recording the nested error, catalog name, and elapsed merge time; those fields explain why consolidation stopped.
Master merge checkpoints · Merging indexes · Catalog format
Looking for a different code? Search another status or error code.