Starting replication when open commit cycles exist - assure_mimix - 10.0

Assure MIMIX Operations Guide

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Operations Guide
Copyright
2023
First publish date
1999
Last updated
2024-03-12
Published on
2024-03-12T11:06:36.794496

Open commit cycles may be present when a data group ends, or if a system event or failure occurred. In most conditions, an open commit cycle present at the time that a data group ended will not prevent a request to start replication from running.

However, certain operations, such as those listed in When to clear pending entries and entries in error when starting a data group or when performing a hardware upgrade with a disk image change, require a clear pending start after they are performed, Therefore, open commit cycles must be resolved before performing the operation.

MIMIX will prevent the data group from starting with open commit cycles when any of these conditions exist:

  • When the start request specifies to clear pending entries. Certain procedures may require a clear pending start. Message LVE387F is issued with reason code AP.

  • When the commit mode specified for the database apply process changed. Changing the commit mode is not a common occurrence. Message LVEC0B3 is issued.

  • When you are changing the target constraint management value specified for the database apply process from *YES to NO in a data group that existed and used target constraint management prior to upgrading to MIMIX version 9.0.

When these conditions exist, the open commit cycles must be resolved.