You are on page 1of 2

SAP Note

912425 - AIX: Unexplained high memory consumption


Version 4 Validity: 30.04.2007 - active

Language English

Header Data
Released On
Release Status
Component

29.05.2007 06:44:32
Released for Customer
BC-CST-MM Memory Management

Other Components BC-OP-AIX IBM AIX


Priority
Category

Correction with high priority


External error

Symptom
High memory consumption occurs in the extended memory on AIX, without an apparent cause.
The problem concerns the special implementation of the extended memory for AIX that is activated by
the parameter ES/TABLE = SHM_SEGS.
The problem occurs if the segment size that is set with parameter ES/SHM_SEG_SIZE is 4GB or greater.
As of kernel release 640, the size is set to 4GB by default:
ES/SHM_SEG_SIZE = 4096
Note that this note is only valid as of kernel release 6xx.

Other Terms
disclaim

Reason and Prerequisites


The AIX function disclaim(), which is used for releasing real memory to AIX in the extended memory,
is not 64-bit secure.
The argument that specifies the length of the area to be released is of the type "unsigned
int" (meaning 32-bit), and is therefore unable to describe a length of exactly 4GB or greater. See
the man page of disclaim.
When the
extended
the real
the case

SAP-kernel was released from the 32-bit restrictions, the default segment size in the
memory for AIX was also increased to 4GB. disclaim() is therefore no longer able to release
memory contained in the segment if the operation is applied to the entire segment. This is
if a segment is released in full by a user context.

Solution
You can avoid the problem by using the following patch levels and setting the parameter
(ES/SHM_SEGS_VERSION = 2):
6.40: 126
7.00:57
Note 856848 contains further information about this parameter.
The problem can also be avoided without this patch if you set the segment size smaller than 4GB, for
example, if you use the parameter:
ES/SHM_SEG_SIZE = 2048; default value is 4096
The maximum size of a user context is given from the product
< ES/SHM_MAX_PRIV_SEGS x ES/SHM_SEG_SIZE >
You may need to increase the parameter ES/SHM_MAX_PRIV_SEGS if user contexts are likely to become
very large.
If you change ES/SHM_MAX_PRIV_SEGS, then you must also adjust parameter ES/SHM_PROC_SEG_COUNT to the
total of ES/SHM_MAX_PRIV_SEGS and ES/SHM_MAX_SHARED_SEGS
ES/SHM_MAX_PRIV_SEGS plus ES/SHM_MAX_SHARED_SEGS

Validity
Software Component From Rel.
SAP_BASIS
610
700
710

To Rel. And Subsequent


640

700

710

References
This document refers to:
SAP Notes
856848 AIX Extended Memory Disclaiming

This document is referenced by:


SAP Notes (1)
856848 AIX Extended Memory Disclaiming