Skip to content
Keressen, hogy többet megtudjon az InterSystems termékeiről és megoldásairól, karrierlehetőségekről és még sok másról.

Alert: Potential Integrity Issue with Mirroring

July 6, 2016 – Alert: Potential Integrity Issue with Mirroring

InterSystems has corrected a defect with Mirroring that can impact data integrity.

The defect is present in all released versions Caché, Ensemble, and HealthShare beginning with 2015.2.0. It is present for all platforms and affects both failover and asynchronous mirroring configurations.

The nature of the defect is that updates may be skipped when journals are applied to a non-primary system. The defect is only triggered under certain unusual conditions when a non-primary mirror member is starting or reconnecting.

InterSystems recommends, in addition to obtaining the correction, that at-risk systems be checked for impact. There are two methods to do this:

  1. A utility, available via FTP here, can be used to scan a series of cconsole.log files and determine that a system has not been impacted. To ensure a complete check the routine must scan all cconsole.log files generated since a system was upgraded to 2015.2+. Load it in any namespace and invoke it interactively with ‘do ^SML2330Alert’.
  2. The ^DATACHECK utility can be used to check that destination and source systems are in sync.

If either check indicates a problem, please contact InterSystems Worldwide Response Center (WRC) for further assistance. The affected mirror member may need to be rebuilt; information on rebuilding a mirror member can be found here.

The correction for this defect is identified as SML2330. It will be included in all future product releases including the upcoming 2015.2.4 and 2016.1.2 maintenance distributions. It is also available via ad hoc distribution as a patched routine. If you have any questions regarding this alert, please contact InterSystems 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.