Solution : https://service.sap.com/sap/support/notes/153641 (SAP Service marketplace login required)
Summary :
Insufficient swap space on 64-bit R/3 systems results in application server startup failures, inability to create memory buffers, and runtime errors due to memory shortages (error codes: ENOMEM, ENOSPC). The problem arises because 64-bit environments require a substantially larger address space to facilitate zero-administration memory management. To address this, it is recommended to configure at least 20 GB of swap space for a single 64-bit instance, plus additional 10 GB for each extra instance on the same server. This scale ensures efficient memory management and aids in avoiding program terminations and costly downtime related to memory issues, creating cost-effectiveness in maintenance and support activities.
Key words :
setting sufficiently large default values, heap storage_parameters_wrong_set additional key words, customizing individual storage areas, costs effective solution compared, virtual adress space arising, entire address space required, symptom insufficient swap space, large btc-wps 2, virtual address space, 0 gb heap requirements
Related Notes :
| 1310037 | SUSE LINUX Enterprise Server 11: Installation notes |
| 1262987 | Swap space requirement for R/3 64-bit kernel installation PI |
| 1121904 | SAP on AIX: Recommendations for paging space |
| 1112627 | SAP on HP-UX: Recommendations for swap and pseudo swap |
| 1075118 | SAP on HP-UX: FAQ |
| 790099 | R/3 Parameter Settings for Unicode conversion |
| 570375 | SAP on Sun Solaris: Swap Space and Paging |
| 192822 | FAQ: 32-bit/64-bit R/3-oracle |
| 171356 | SAP software on Linux: General information |
| 146289 | Parameter Recommendations for 64-Bit SAP Kernel |