Solution : https://service.sap.com/sap/support/notes/922352 (SAP Service marketplace login required)
Summary :
If you activate the "mapped" memory management option (es/implementation=map) in SAP, you might receive a warning in the dispatcher trace file indicating a configuration issue where the initial memory size setting (em/initial_size_MB) exceeds the maximum memory size (em/max_size_ MB). This misconfiguration can hinder the SAP Kernel's ability to extend the SAP Extended Memory when necessary, potentially forcing work processes into PRIV mode due to full utilization of SAP EM. To resolve, do not manually set these parameters in Linux but allow the SAP Kernel to adjust them based on PHYS_MEMSIZE. For manual adjustments, ensure that em/max_size_MB is equal to or greater than em/initial ```
Key words :
memory management implementation activated, warning => <esmap> em/initial_size_mb, es/implementation=map, sap extended memory, dispatcher trace file, priv mode reason, running sap applications, sap kernel calculate, terms em/initial_size_mb, parameters em/initial_size_mb
Related Notes :
| 386605 | SAP Memory Management for Linux (32-bit) |
| 171356 | SAP software on Linux: General information |