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

Alert: Database Integrity on UNIX® and Linux Platforms

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:

PlatformVersions 2012.1 to 2015.1Version 2015.2 and later
AIXOptionalAlways on
HP/UXOptionalAlways on
Linux (all)OptionalOptional
MacOSOptionalAlways on
SolarisOptionalAlways on

For platforms where asynchronous I/O is optional, you can determine if it is in use by examining the cconsole.log file. In that file, at instance startup, locate a reference to:

swdwrtmax=

If this is set to a non-zero value, then asynchronous I/O is in use.

It is only possible to trigger this defect when a hardware or OS-level I/O error occurs while writing to storage AND the environment recovered without needing to be restarted (that is, the environment did not hang). Such an I/O error may result in the following corresponding message in the cconsole.log:

****** SERIOUS DISK WRITE ERROR - WILL RETRY ******

However, a write error can occur without triggering the defect. (That is, the presence of an I/O error or a cconsole.log message does not guarantee that the defect has been triggered.)

If a system has experienced the above, check the integrity of databases on the affected storage via the InterSystems integrity check utility.

The correction for this defect is identified as JO2950. It will be included in all future releases of Caché, Ensemble, and HealthShare. 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: