InterSystems has corrected a defect that can cause corruption of databases and journal files on AIX systems with IBM POWER8 or later POWER processors. This defect can be triggered only when database or journal encryption is in use.

 To trigger this defect, the following conditions are required:

• The environment uses database or journal encryption
• The environment also uses data-element encryption
• An encryption key used for data-element encryption has been deactivated

If the environment satisfies all these conditions, then the key schedule used for database or journal encryption can become

InterSystems has corrected a defect that can result in Enterprise Cache Protocol (ECP) client instability under rare conditions.

The defect exists in the following products and any InterSystems offerings based on them.

Impacted versions are 2022.1.x, 2022.2, and 2022.3:

InterSystems IRIS®

InterSystems IRIS for Health™

HealthShare® Health Connect

Impacted version is 2022.2 (only for customers deploying ECP):

InterSystems HealthShare®

The issue can only occur on ECP client systems.

InterSystems has corrected a defect that causes incorrect ObjectScript routine compilation.

This defect exists only in the recently released 2021.1.1 version of:

            InterSystems IRIS Data Platform

            InterSystems IRIS for Health

            HealthShare Health Connect

InterSystems recommends that 2021.1.1 not be used.

InterSystems has corrected a defect that can result in an SQL query returning incorrect results.

This defect exists only in the 2021.2 (Continuous Delivery) version of:

            InterSystems IRIS Data Platform

            InterSystems IRIS for Health

            HealthShare Health Connect

InterSystems has replaced existing distributions of these products with new builds that correct the defect. The corrected distributions can be identified by the build number (651) and are available via normal means. Ad Hoc corrections are not available for Continuous Delivery (CD) distributions.

This defect

In light of the COVID-19 situation worldwide, InterSystems is working to ensure continuous support for our customers, promote the health and well-being of our employees, and protect the communities where we live and work. Please view our statement and frequently asked questions.

In addition, we have also established a special email address, COVID-19@InterSystems.com, should you have any questions or concerns.

As we have for 41 years, we stand by our commitment to customers and are prepared to support you during this challenging time.

Sincerely, 

John Paladino

Vice President, Client Services

InterSystems has corrected a defect that can cause shadowing to fail with an access violation. In rare cases, the defect can cause memory corruption, leading to unpredictable behavior. 

Note: The defect does not affect mirroring.

This defect affects:

• InterSystems IRIS 2019.1.1 and 2019.3
• IRIS for Health 2019.1.1 and 2019.3
• HealthShare Health Connect 2019.1.1
• HealthShare Health Connect (HSAP) 15.032 on 2018.1.3
• Caché and Ensemble 2018.1.3

In InterSystems IRIS and IRIS for Health, shadowing code is included, but it should not be used; InterSystems recommends using mirroring, which is not

InterSystems has corrected a defect that can result in application data integrity issues following an abnormal shutdown.

This problem exists for:

• Caché and Ensemble 2018.1.2
• HealthShare Health Connect (HSAP) 15.032 on Core version 2018.1.2
• InterSystems IRIS Data Platform 2019.1
• InterSystems IRIS for Health 2019.1
• HealthShare Health Connect 2019.1

The defect breaks the journal sync guarantee that all updates in the journal buffer have been written to the journal file. The failure is silent: it does not generate an error message and there is no entry about it in any log file.

Specifically,

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.

October 12, 2018 – Advisory: VMWare vSphere and Data Integrity

Clients running vSphere 5.5 or later should review a very important article that VMware published on October 9, 2018.  The article describes the possibility of file system and database corruption, which can lead to outages and possible data loss.  We have confirmed that this has caused data integrity problems for InterSystems clients. Therefore, we encourage you to act on this as soon as possible.

The VMWare knowledge base article is titled:

Virtual Machines running on an SEsparse snaposhot may report guest data inconsistencies

October 12, 2018 – Alert: Ordering of XML Sibling Elements

InterSystems has corrected a defect that can cause a reordering of sibling elements in an XML document. This issue is limited to sibling elements that are represented in the database as objects in a relationship.

This problem exists on all platforms for the following products:

• InterSystems IRIS Data Platform 2018.1.0 and above
• InterSystems IRIS for Health 2018.1.2
• Caché and Ensemble 2017.2.0 and above
• Health Connect/HSAP based on Caché/Ensemble 2017.2.0 and above

Note: HealthShare functionality has been reviewed and is not impacted by this

September 24, 2018 – Advisory: VMWare vSAN and Data Integrity

Clients running vSAN 6.6 or later should review a very important article that VMware published on September 21, 2018.  The article describes the possibility of file system and database corruption, which can lead to outages and possible data loss, and we believe that some of our clients have encountered this issue.  Therefore, we encourage you to act on this as soon as possible.

The VMWare knowledge base article is titled:

Virtual Machines running on VMware vSAN 6.6 and later report guest data consistency concerns following a disk extend operation (58715)

June 25, 2018 – Alert: Outer Join Query Results

InterSystems has corrected two defects that can cause SQL outer joins to return incorrect results. These defects can also impact DeepSee in Caché and Ensemble, as well as InterSystems Business Intelligence in InterSystems IRIS; in these cases, building and synchronizing some analytic models may result in build errors.

These issues exist on all platforms for the following released InterSystems Data Platform products:

• InterSystems IRIS Data Platform 2018.1.1
• Caché and Ensemble 2017.2.0 and 2017.2.1
• HealthShare Health Connect 15.03 on Ensemble

This document describes considerations around SDDC and HCI solutions for InterSystems Clients.

Software Defined Data Centers (SDDC) and Hyper-Converged Infrastructure (HCI) – Important Considerations for InterSystems Clients

A growing number of IT organizations are exploring the potential use of SDDC and HCI solutions.

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

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.

November 22, 2016 – Alert: Database Integrity on UNIX^® and Linux Platforms

InterSystems has corrected a defect that may, in rare circumstances, result in database degradation on UNIX and Linux platforms.

This defect affects Caché, Ensemble, and HealthShare distributions beginning with Caché version 2012.1. It is only a possible risk on UNIX and Linux platforms that are using asynchronous I/O for database writes. The following table specifies if asynchronous I/O is always on or optional for the affected platforms and releases:

InterSystems has corrected a defect that may result in missing updates when utilizing Caché online backup.

This defect is present in all Caché and Ensemble versions 2015.1.x, 2015.2.x and 2016.1.x, and all HealthShare distributions based on those versions.  It affects all platforms and operating systems except backups of OpenVMS cluster databases.

The risk does not exist for Mirror Catchup applied to mirrored databases restored from Caché online backup.

The risk only exists when restoring from Caché online backup and applying journal files.

August 24, 2016 – Alert: Database Compaction

This is an addendum to the Alert published on October 14, 2015 – Alert: Database Defragmentation.

That alert indicated that the database defragmentation utility in 2014.1 and higher, on all platforms except OpenVMS, could cause database degradation and the correction JO2871 is available to clients upon request and would be included in future releases.  The correction was included in 2015.1.3, 2015.2.2 and 2016.1.