Skip to content
Suchen Sie nach Produkten und Lösungen von InterSystems, Karrieremöglichkeiten und mehr.

Alert: Possible Data Integrity Issues after Adding Mirrored Database

April 2, 2020 – Alert: Possible Data Integrity Issues after Adding Mirrored Database

InterSystems has corrected a defect that can result in data integrity issues on systems using mirroring.

This defect affects:

  • All currently released versions of InterSystems IRIS and IRIS for Health, except 2020.1
  • Caché and Ensemble versions beginning with 2011.1.1
  • All HealthShare products based on the above Data Platforms versions

This defect is more likely to be encountered in IRIS and IRIS for Health 2019.4. It is highly unlikely to have occurred on deployed systems running any other version.

The issue can only occur in a situation that meets all of the following conditions:

  1. A database is removed from a mirror
  2. A database is added to the same mirror – this can be the same database or another one
  3. There is no journal switch between removing the first database and adding the second one.

If a system encounters the defect, then the current journal file will be intact on the primary system where the database was added, but a small subset of updates in that journal file will be missing from the newly added mirrored database on all other mirror members – both failover and async members. All updates from subsequent journal files are correctly dejournaled.

There is no way to definitively determine if the defect has been encountered, but you can use the DataCheck utility to confirm the consistency of a mirror set. For more information about DataCheck, see the “ Data Consistency On Multiple Systems” section of the Data Integrity Guide.

The correction for this defect is identified as HYY2390 and will be included in all future product releases. It is also available by requesting an Ad hoc distribution from the InterSystems Worldwide Response Center (WRC).

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

Latest Alerts & Advisories

15 Aug 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.
24 Jul 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.
24 Jun 2024
Broadcom recently announced a problem that can cause data consistency errors in database applications. The Broadcom article is available here:
30 May 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.
01 May 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.
08 Apr 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.
19 Mar 2024
In evaluating an IBM Support notification, InterSystems has determined a potential impact for our customers. The notification in question is:
27 Feb 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.
01 Feb 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.