Skip to content
Effectuer une recherche pour en savoir plus sur les produits et solutions InterSystems, les offres d'emploi, etc.

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.

 

Latest Alerts & Advisories

15 Aug 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.
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.