Skip to content
Use the search to find information about InterSystems products and solutions, career opportunities, and more.

Alert: Database Corruption with Multi-Volume Databases after Truncation

InterSystems has corrected a defect that can cause database corruption or <DISKHARD> errors with multi-volume databases under extremely rare circumstances. Only databases that have been truncated are at risk.

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

  • InterSystems IRIS® – 2024.1, 2024.1.1, and 2024.2
  • InterSystems IRIS® for Health – 2024.1, 2024.1.1, and 2024.2
  • HealthShare® Health Connect – 2024.1, 2024.1.1, and 2024.2

No HealthShare Solutions products are affected by this defect.
Although InterSystems has received no reports from customers due to this defect, we recommend the following temporary mitigation to avoid the problem:

  • Do not truncate multi-volume databases.
  • Do not create a new volume for a single- or multi-volume database that you have truncated since the last time the database was mounted. To disable automatic creation, set the configuration parameter New Volume Threshold = 0.  Note that setting this parameter does not prevent manual creation of new volumes.

The correction for this defect is identified as DP-433375. It will be included in all future versions and is also available via Ad-hoc distribution.
If you have any questions regarding this alert, please contact the Worldwide Response Center.

Latest Alerts & Advisories

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.