Alert: System Hang with ≥ 2 TB Database Cache
Summary
| Alert Id | Product & Versions Affected | Risk Category & Score | Explicit Requirements |
| DP-448888 |
Products: Versions: |
Operational: High Risk | ≥ 2 TB of database cache is used |
Issue
In the versions specified above, an instance may fail to start or may hang during operation if the database cache is greater than or equal to 2,097,152 MB (2 TB). Note that the initial database cache allocation for an unconfigured instance is 25% of the system’s physical memory; hence, an unconfigured instance may be at risk if it there is ≥ 8 TB of physical memory. For more information, see Allocating Memory to the Database and Routine Caches and the database cache (globals) configuration parameter.
If you used the advanced configuration option to allocate buffers of multiple block sizes, then you must calculate the limit in units of global buffers. There is no risk as long as the total number of buffers of all sizes combined is fewer than 268,435,456.
This issue affects versions 2024.3, 2025.1.0 – 2025.1.3, 2025.2.0, and 2025.3.0 of the following products:
- InterSystems IRIS
- InterSystems IRIS for Health
- InterSystems Health Connect
Impact Assessment
- An instance may fail to start or may hang during operation if the database cache is greater than or equal to 2,097,152 MB (2 TB).
- If your instance has more than 2 TB of database cache, reduce it based on the guidance above.
- The issue has been corrected in versions 2026.1.0 and 2025.1.4:
- 2026.1.0 is scheduled for availability on March 25, 2026.
- 2025.1.4 is scheduled for availability on April 15, 2026.
- In the interim, customers who require the correction prior to these releases may request an ad hoc distribution for the fix (DP-448888) through the Worldwide Response Center.
For More Information
If you have questions or need assistance, please contact the InterSystems Worldwide Response Center (WRC).