Skip to content
Busque para obtener información sobre los productos y soluciones de InterSystems, las oportunidades de carrera y más.

Alert: Linux Defects Can Corrupt Mirror Copies of Journal Files


July 27, 2017 – Alert: Linux Defects Can Corrupt Mirror Copies of Journal Files

InterSystems has encountered defects in Linux which can corrupt copies of journal files that are generated on a mirror backup or async member; this occurs only in certain specific configurations. The original mirror journal file created on the primary member is not affected.

The risk is only exposed in Caché, Ensemble, and HealthShare distributions beginning with version 2017.1.0. The risk only exists on Linux and only if a backup or async mirror member is configured to use the rtkaio library.

The rtkaio library is distributed with Red Hat Enterprise Linux, though it may be possible to acquire it for other Linux distributions. Caché does not use the rtkaio library by default. Therefore, the risk does not exist unless your system has been configured to use rtkaio. Sites most commonly configure Caché to use rtkaio via the LibPath parameter in cache.cpf.

When the problem is triggered, copies of mirror journal files retrieved on a backup or async mirror member may become corrupted. This typically results in errors during dejournaling of the corrupt file and an alert in the cconsole.log similar to:

03/29/17-16:18:12:852 (25129) 2 Dejournal stuck at 7342380 (0x0070092c) cyclejrnend=11141120 in file #9

InterSystems has notified Red Hat about this issue. Until a correction becomes widely available in supported Linux releases, InterSystems offers a workaround for sites that have configured Caché to use rtkaio. This workaround automatically removes any occurrence of rtkaio from the library path for the daemon process that writes these copies of mirror journal files.

Note that the workaround is not effective if rtkaio use was configured by manipulating the library files rather than setting the LibPath parameter.

The workaround is identified as RJF264 and will be included in all future releases of Caché, Ensemble, and HealthShare. The workaround 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

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.
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.
Jan 17, 2024
This problem affects the following products: