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

Alert: Write Image Journal failure

March 11, 2015 – Alert: Write Image Journal failure

InterSystems has corrected a defect that may cause data integrity issues following a crash on systems with a certain unusual configuration.  Specifically, the defect can cause application of the WIJ file to fail during startup.

A detailed discussion of the protection provided by the WIJ can be found in the Caché Data Integrity Guide.

This defect is present in all currently released versions of Caché, Ensemble, and HealthShare.  It affects all platforms and operating system versions.

The only systems vulnerable to this defect are those that mount hundreds of databases referenced by long path names.  When the combined length of the path names exceeds approximately 32,000 characters, the defect can occur. The exact condition can be checked for a given system by running the following command:

For Windows:

<install-directory>bincwdimj -d2 -j<wij-directory>

For Unix/Linux

<install-directory>/bin/cwdimj -d2 -j<wij-directory>

For OpenVMS

Define a foreign command

$ cwdimj :== $sys$disk:[-.bin]cwdimj.exe

and from the cachesys manager’s directory issue:

$ cwdimj –d2 –j_<wij-directory>

 

The output of this command will include the value of “Dirlen”.  If Dirlen is less than or equal to 32768, the system is not currently exposed to this defect.  Please note that the value of Dirlen changes as you add or remove databases to your running environment.  If Dirlen is close to the limit of 32768, InterSystems recommends that you request the correction identified below.

If a system exposed to this defect shuts down abnormally, and the abnormal shutdown occurs at a time when there are database blocks pending in the WIJ, startup will fail necessitating manual deletion of the WIJ. This causes database integrity issues. If this occurs, an entry similar to the following will be present in the cconsole log file:

Starting WIJ recovery for '

CACHE.WIJ'.

N>0 blocks pending in this WIJ.

WIJ pass # is 0.

WIJ file does not match expectations: XXXXX

 

The correction for this defect is identified as JPL1675.  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 advisory, please contact the Worldwide Response Center.

 

最新警报和通知

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所有版本的产品。
Apr 28, 2023
InterSystems 已修复了一个缺陷,该缺陷可能会导致使用 IBM POWER8 或更高版本的 POWER 处理器的 AIX 系统上的数据库和Journal日志文件损坏。只有在使用数据库或Journal日志加密时才会触发此缺陷。
Apr 11, 2023
InterSystems已修复一个缺陷,该缺陷在罕见情况下会导致ECP客户端不稳定。
Apr 06, 2023
InterSystems 已修复一个导致SQL查询返回不正确结果的缺陷。该缺陷存在于以下产品和基于这些产品的任何InterSystems产品中。