A leak in shared memory can lead to failed snapshot backup operations and unsuccessful database restarts.
Details
| Detail name | Value |
|---|---|
| Changelog Number | 27051 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.29.0, Exasol 2025.1.0, Exasol 2025.2.0 |
| Fix Versions | Exasol 2025.1.9, Exasol 2025.2.1 |
| Resolution Date | 2026-02-18 |
Description
All databases in our SaaS environment use snapshot backups. We have identified a memory leak in the shared memory that occurs during certain snapshot backup operations. Over time, this leak accumulates and eventually prevents further snapshot backups from being performed. In some cases, the memory leak also prevents the affected databases from restarting successfully.
Workaround
Restart the database and all AWS instances. In SaaS environment restarting of AWS instances could be performed only by Exasol Support.
Fix
The memory leak in the shared memory has been fixed and the system is working without problems.
