DB2 - Problembeschreibung
Problem IC77856 | Status: Geschlossen |
DB2 INCORRECTLY RELEASES SHARED MEMORY ON LINUX, LEADING TO PAGING, PERFORMANCE DEGRADATION | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
DB2 is intending to use the MADV_REMOVE flag on Linux to decommit memory with the madvise() API, but instead is falling back to a weaker MADV_DONTNEED flag. This is due to an incorrect attempt to use MADV_REMOVE with memory mapped stack memory. As a result, DB2's shared memory is not being decommitted, but only unmapped. Memory is not being released dynamically by DB2 as expected and is also highly eligible for paging out, which can later result in performance degradation on page-ins if DB2 wants to reuse the memory. STMM will also not account for this memory in its target calculations, since it appears in memory statistics as though it were clean file cache pages, and available for other use. This leads to memory overcommitment in STMM-tuned environments. Please note that vm.swappiness should be set to 0 for DB2 systems, otherwise this may result in system swapping when there is no memory overcommitment. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All DB2/Linux systems * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 5 or higher * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
Problem first fixed in DB2 Version 9.7 Fix Pack 5 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC78091 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 31.07.2011 22.12.2011 22.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |