Skip to content
Telusuri untuk mempelajari tentang produk dan solusi InterSystems, peluang karier, dan banyak lagi.

Alert: Data Corruption with Mixed Endian Mirror Shadowing

June 26, 2017 - Alert: Data Corruption with Mixed Endian Mirror Shadowing

InterSystems has corrected a defect that may result in corruption of Unicode data on a shadow system whose source is an async mirror member.

This defect affects all currently released Caché, Ensemble, and HealthShare distributions beginning with version 2012.2.0.  All platforms and operating systems are affected.

In order to be exposed to the risk the configuration must include mirror primary and async members, and a shadow of the async member.  Additionally, the async member must be of different endian than both the primary mirror member and the shadow.

Primary (endian X) -> Async (endian Y) -> Shadow (endian X)

In the above configuration, some Unicode strings greater than 255 characters on the shadow member may be corrupt for databases that are shadowed from the async.

If you are unsure of the endianness of your systems, see the InterSystems Supported Platform (ISP) document.

At the time the data is applied to the shadow member there is no indication of a problem.  Depending on the corruption there may also be no error triggered when the corrupt data is accessed.  The only definitive way to detect the corruption is by comparing the data value between the async member and the shadow.
The correction for this defect is identified as HYY2192. It will be included in all future releases of Caché, Ensemble, and HealthShare, including the just released 2016.1.4.  The correction is also available via Ad Hoc distribution from InterSystems Worldwide Response Center (WRC). If you have any questions regarding this alert, please contact the Worldwide Response Center.

RELATED TOPICS

Latest Alerts & Advisories

15 August, 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.
25 July, 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 June, 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 April, 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 March, 2024
In evaluating an IBM Support notification, InterSystems has determined a potential impact for our customers. The notification in question is:
27 February, 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 February, 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.
17 January, 2024
This problem affects the following products: