Skip to content
搜索以了解InterSystems产品和解决方案,职业机会等。

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.

最新警报和通知

Aug 21, 2024
InterSystems 已修复了一个缺陷,在极少数情况下,该缺陷可能导致多卷数据库出现数据库损坏或 错误。只有被截断的数据库才存在风险。
Jun 03, 2024
从发布InterSystems IRIS®数据平台2022.3开始,InterSystems修改了许可证强制执行机制,以包括REST和SOAP请求。由于这种变化,在升级后,使用REST或SOAP的非处理器核数的许可证环境下,用户可能会遇到更高的许可证消耗。要确定此警报是否适用于您的InterSystems许可证,请按照下面链接的FAQ中的说明进行操作。
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.
Nov 14, 2023
There are 10 alerts in the HealthShare HS2023-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: HS2023-02-Communication.
Jun 17, 2023
InterSystems 已纠正导致进程内存使用量增加的缺陷。
May 11, 2023
InterSystems已经解决了影响Caché、Ensemble、HealthShare、InterSystems IRIS、InterSystems IRIS for Health、HealthShare HealthConnect和TrakCare的安全漏洞。 这些漏洞影响到InterSystems所有版本的产品。
Apr 28, 2023
InterSystems 已修复了一个缺陷,该缺陷可能会导致使用 IBM POWER8 或更高版本的 POWER 处理器的 AIX 系统上的数据库和Journal日志文件损坏。只有在使用数据库或Journal日志加密时才会触发此缺陷。
Apr 11, 2023
InterSystems已修复一个缺陷,该缺陷在罕见情况下会导致ECP客户端不稳定。
Apr 06, 2023
InterSystems 已修复一个导致SQL查询返回不正确结果的缺陷。该缺陷存在于以下产品和基于这些产品的任何InterSystems产品中。