Skip to content
Sök för att lära dig mer om InterSystems produkter och lösningar, karriärmöjligheter med mera.

Alert: Data Integrity Issue with Mirror Database Catchup

March 14, 2019 – Alert: Data Integrity Issue with Mirror Database Catchup

InterSystems has corrected a defect in our mirroring technology that can result in inconsistency between mirrored databases. This defect exists for currently released Caché and Ensemble versions beginning with 2017.2 and for InterSystems IRIS Data Platform version 2018.1.

When the issue occurs, some journal updates are not applied to a mirrored database on the backup mirror member or an async member that is being caught up. The result is that the database may not be synchronized with the database on the primary mirror member.

This problem can occur only if a mirror member shuts down abnormally during the Catchup operation. The abnormal shutdown can result from either:

  • A forced shutdown of the instance
  • An operating system shutdown or crash

Note that, even when all necessary conditions exist, the likelihood of experiencing the impact of this defect is very low.

Determining if a system has been affected

First, determine if a Catchup operation was ever interrupted by an abnormal shutdown:

  1. Search the chain of cconsole.log files (for Caché and Ensemble) or messages.log files (for InterSystems IRIS) since installing or upgrading to an impacted product version.
  2. Look for the strings “catchup started for” and “Mirror Catchup completed for”, which indicate the start and end of a Catchup operation.

If an abnormal shutdown did not occur between the start and end of a Catchup, the instance has not been affected; if there has been an abnormal shutdown during a Catchup, this means that the instance may have been affected.

Second, if an abnormal shutdown did occur during a Catchup operation, determine if the mirrored databases are currently inconsistent. Run DataCheck to verify the consistency of globals across mirror members. Verification by DataCheck does not guarantee that the data was consistent at all times, as subsequent updates of impacted globals may have brought them back to consistency. For more information on DataCheck, see the “Data Consistency on Multiple Systems” chapter in the Data Integrity Guide.

Information about the correction

The correction for this defect is identified as JO3114. It is included in Caché and Ensemble releases beginning with 2018.1.2 and in InterSystems IRIS Data Platform releases beginning with 2019.1. The correction is also available from the Worldwide Response Center (WRC) via Ad hoc distribution.

If you have any questions regarding this alert, please contact the Worldwide Response Center.

Latest Alerts & Advisories

Aug 15, 2024
InterSystems has corrected a defect that can cause database corruption or errors with multi-volume databases under extremely rare circumstances. Only databases that have been truncated are at risk.
Jul 24, 2024
There are four alerts in the HS2024-03 Alert Communication. A summary of each alert is shown below. Details for each alert are contained in the linked document.
Jun 24, 2024
Broadcom recently announced a problem that can cause data consistency errors in database applications. The Broadcom article is available here:
May 30, 2024
Beginning with the release of InterSystems IRIS® data platform 2022.3, InterSystems corrected the license enforcement mechanism to include REST and SOAP requests. Due to this change, environments with non-core-based licenses that use REST or SOAP may experience greater license utilization after upgrading. To determine if this advisory applies to your InterSystems license, follow the instructions in the FAQ linked below.
May 01, 2024
InterSystems has corrected an issue that can cause a small number of SQL queries to return incorrect results. See below for the specifics on impacted queries.
Apr 08, 2024
InterSystems has encountered a defect that causes some upgrades of HealthShare® Health Connect to fail. This only affects instances that are not licensed for the use of FHIR® and that have interoperability-enabled namespaces. Under these conditions, the upgrade fails with an error.
Mar 19, 2024
In evaluating an IBM Support notification, InterSystems has determined a potential impact for our customers. The notification in question is:
Feb 27, 2024
There is 1 alert in the HealthShare HS2024-limited Alert communication. An alert summary for the issue is shown is in the table below. Details for the alert are contained in the attached document: HS2024 Limited Communication.
Feb 01, 2024
There are 2 alerts in the HealthShare HS2024-02 Alert communication. An alert summary for each issue is shown is in the table below. Details for each alert are contained in the attached document: HS2024-02-Communication.