Direct links to fixes
8.1.1.200-IBM-SPSRV-AIX
8.1.1.200-IBM-SPSRV-Linuxppc64le
8.1.1.200-IBM-SPSRV-Linuxs390x
8.1.1.200-IBM-SPSRV-Linuxx86_64
8.1.1.200-IBM-SPSRV-WindowsX64
8.1.5.100-IBM-SPSRV-AIX
8.1.5.100-IBM-SPSRV-Linuxppc64le
8.1.5.100-IBM-SPSRV-Linuxs390x
8.1.5.100-IBM-SPSRV-Linuxx86_64
8.1.5.100-IBM-SPSRV-WindowsX64
8.1.6.000-IBM-SPSRV-AIX
8.1.6.000-IBM-SPSRV-Linuxppc64le
8.1.6.000-IBM-SPSRV-Linuxs390x
8.1.6.000-IBM-SPSRV-Linuxx86_64
8.1.6.000-IBM-SPSRV-WindowsX64
8.1.6.000-IBM-SPOC-AIX
8.1.6.000-IBM-SPOC-LinuxPPC64le
8.1.6.000-IBM-SPOC-Linuxs390x
8.1.6.000-IBM-SPOC-Linuxx86_64
8.1.6.000-IBM-SPOC-WindowsX64
8.1.6.000-IBM-SPCMS-Linuxx86_64
8.1.6.000-IBM-SPCMS-WindowsI32
8.1.6.000-IBM-SPCMS-WindowsX64
8.1.6.100-IBM-SPSRV-Linuxppc64le
8.1.6.100-IBM-SPSRV-AIX
8.1.6.100-IBM-SPSRV-Linuxs390x
8.1.6.100-IBM-SPSRV-Linuxx86_64
8.1.6.100-IBM-SPSRV-WindowsX64
IBM Spectrum Protect Server V8.1.1.X interim fix downloads
IBM Spectrum Protect Server V8.1.5.X interim fix downloads
IBM Spectrum Protect Server V8.1 Fix Pack 6 (V8.1.6) Downloads
IBM Spectrum Protect Server V8.1.6.X interim fix downloads
APAR status
Closed as program error.
Error description
Running IBM Spectrum Protect server on Linux platform, the Operating System can invoke the oom-killer as indicated in the Linux system logs as such due to high resident memory usage: Feb 8 04:24:27 localhost kernel: [369070.133339] dsmserv invoked oom-killer: gfp_mask=0x26000c0, order=2, oom_score_adj=0 < ... > Feb 8 04:24:27 localhost kernel: [369070.133694] Out of memory: Kill process 19360 (db2sysc) score 405 or sacrifice child which will cause db2 and dsmserv to stop. The amount of memory held by the Operating System for the IBM Spectrum Protect server process is growing, but is not actually being used by the server. The IBM Spectrum Protect server is deallocating memory but the Operating System is not releasing that memory to be reused, thus the Operating System will show a much higher "resident memory" value then what is reported in IBM Spectrum Protect server's "show alloc" command. For example, running "top" on the system could show a "res" (resident memory) value of 30 GB for dsmserv, while IBM Spectrum Protect server could only show 20 GB of allocated space in the "show alloc" command. Note that these numbers will never exactly match, but there should not be such a large discrepancy. So over time, the memory usage will increase, such that free memory reduces and the Operating System has to invoke oom-killer. Initial Impact: Medium IBM Spectrum Protect versions affected: Server 7.1.3.x and higher, and 8.1..x and higher on all Linux platforms Additional Keywords: TSM Spectrum Protect memory RTC162936
Local fix
Restart Linux server to free memory
Problem summary
**************************************************************** * USERS AFFECTED: * * All IBM Spectrum Protect Server users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Apply fixing level when available. This problem is currently * * projected to be fixed in levels 8.1.1.100, 8.1.4.100, and * * 8.1.5.100, and 8.1.6. Note that this is subject to change * * at the discretion of IBM. * ****************************************************************
Problem conclusion
The problem was fixed Affected platforms: AIX and Linux
Temporary fix
Comments
APAR Information
APAR number
IT24079
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
81L
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-02-26
Closed date
2018-05-23
Last modified date
2018-05-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TSM SERVER
Fixed component ID
5698ISMSV
Applicable component levels
Document Information
Modified date:
06 September 2023