Skip to content
搜索以了解InterSystems产品和解决方案,职业机会等。

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

最新警报和通知

Feb 22, 2025
InterSystems 已纠正了两个可能导致少数 SQL 查询返回不正确结果的问题。 此外,InterSystems 还纠正了日期/时间数据类型处理中的不一致性,对于依赖于先前不一致性行为的现有应用程序来说,这种不一致性可能会导致不同的、意想不到的但正确的结果。
Feb 19, 2025
InterSystems 已修复一个缺陷,该缺陷导致在使用特定 $LIST 语法时引入无效的数据库和日志记录。 遇到这种缺陷的可能性很低,但对运营的影响可能很大。
Oct 09, 2024
InterSystems 已经解决了影响 InterSystems IRIS、InterSystems IRIS for Health、HealthShare、HealthShare HealthConnect、TrakCare、Caché 和 Ensemble 的 Web 网关和 CSP 网关的安全漏洞。可从 InterSystems 全球响应中心 (WRC) 获取补救步骤和其他指导文件。在讨论本通知时,请参考 "SVR2024A"。 如需修复帮助,请联系您的应用程序提供商或 InterSystems 全球响应中心。
Aug 21, 2024
InterSystems 已修复了一个缺陷,在极少数情况下,该缺陷可能导致多卷数据库出现数据库损坏或 错误。只有被截断的数据库才存在风险。
Jun 03, 2024
从发布InterSystems IRIS®数据平台2022.3开始,InterSystems修改了许可证强制执行机制,以包括REST和SOAP请求。由于这种变化,在升级后,使用REST或SOAP的非处理器核数的许可证环境下,用户可能会遇到更高的许可证消耗。要确定此警报是否适用于您的InterSystems许可证,请按照下面链接的FAQ中的说明进行操作。
May 01, 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.
Nov 14, 2023
There are 10 alerts in the HealthShare HS2023-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: HS2023-02-Communication.
Jun 17, 2023
InterSystems 已纠正导致进程内存使用量增加的缺陷。
May 11, 2023
InterSystems已经解决了影响Caché、Ensemble、HealthShare、InterSystems IRIS、InterSystems IRIS for Health、HealthShare HealthConnect和TrakCare的安全漏洞。 这些漏洞影响到InterSystems所有版本的产品。