Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
28Activity
0 of .
Results for:
No results containing your search query
P. 1
SAP Note

SAP Note

Ratings: (0)|Views: 4,190|Likes:

More info:

Published by: Adeniran Olusanya Olumide on Jun 11, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

03/31/2013

pdf

text

original

 
SAP Note: 941735. Linux kernelsSummary
Symptom
Recommendation for parameterization of 64-bit Linux systems.
Other terms
Linux memory management, es/implementation, STD, MAP, TMPFS, /dev/shm, 64-bit,em/initial_size_MB
Reason and Prerequisites
For SAP on Linux, two different memory management systems are available. You canswitch between the two systems using the SAP instance profile parameter es/implementation:
MAP implementation (es/implementation=map)This variant is mainly used for 32-bit systems, and is described in detail in Note386605.As of SAP kernel 6.20, an SAP system on Linux uses the MAP implementation bydefault, in which only the currently active user context is displayed in the address spaceof the work process.
STD implementation (es/implementation=std)With this variant, the memory management of an SAP system on Linux is thesame as on standard UNIX systems. This means that all user contexts are displayed in theaddress space at the same time, which means that this variant is only available for 64 bitsystems.While the MAP implementation should be used exclusively on 32-bit Linux in morecases, both variants can be used on 64-bit systems. However, since there are no longer any 32-bit restrictions, there is no longer any need to use the special MAPimplementation on 64-bit Linux systems .
For this reason, the STD implementation for SAP systems on 64-bit Linux isactivated by default as of SAP Kernel 7.10.Solution
 
If you want to use the STD implementation with older SAP kernels, you can activate itusing the profile parameter 
es/implementation=std
.
Relevant parameters for the STD implementationA) SAP profile parameters
em/initial_size_MB
This parameter specifies how much Extended Memory is available to the SAPsystem.In the SAP Extended Memory, there are additional SAP internal memory areas,which cannot be directly accessed by the user contexts. These include the areas that areconfigured using the parameters em/global_area_MB and abap/shared_objects_size_MB. Note: For the user contexts in the system, only the difference of em/initial_size_MB - (em/global_area_MB + abap/shared_objects_size_MB)can be used as Extended Memory.
ztta/roll_extension
This parameter specifies how much SAP Extended Memory is available to anindividual user context.This quota can be set differently for dialog and background work processes if necessary. To do this, use the parameters
ztta/roll_extension_dia
for dialog work  processes or 
ztta/roll_extension_nondia
for background work processes.The three profile parameters used with the MAP implementation(
em/address_space_MB
,
em/max_size_MB
and
PHYS_MEMSIZE
) are not relevant if you use the STD implementation.
B) Linux operating system parameters
The following Linux kernel parameters can be configured using the sysctl interface. Todo this, you must edit the file /etc/sysctl.conf accordingly:
kernel.shmmax
This kernel parameter specifies how large an individual SysV Shared MemorySegment is allowed to be. In the case of an STD implementation, the parameter must beset sufficiently large in order to allow em/initial_size_MB. The value is specified in theunit Bytes so that "21474836480", for example, permits segments of 20 GB.
 
kernel.shmall
This kernel parameter specifies how much SysV Shared Memory is available inthe Linux system as a whole. As an estimate for the requirements of the SAP system, youcan use the total of the SAP Extended Memory (em/initial_size_MB) + SAP buffer (transaction ST02 -> Detail analysis menu -> Storage, row with the entry "Total").If several SAP systems are running on a Linux server, the requirements increaseaccordingly. The same applies for databases that may be operating on the same Linuxserver.As a configuration recommendation, kernel. shmall can be configured as theamount of virtual memory in the Linux system (RAM + Swap).The value is specified in the unit "4 KB blocks", so that "5242880", for example, permits 20 GB SysV Shared Memory in the Linux system as a whole.
TMPFS
With the STD implementation, the SAP Extended Memory is no longer stored inthe TMPFS (under /dev/shm). However, the TMPFS is required by the Virtual MachineContainer (VMC). For this reason, we still recommend the same configuration of theTMPFS:75% (RAM + Swap) is still recommended as the size.
Points to remember when using the STD implementation
Background work processes now use memory close to the process (heap) as thefirst large memory type. The allocation sequence for "NonDia" work processes isas follows:1. Roll memory (ztta/roll_first),2. Heap memory (abap/heap_area_nondia),3. Roll memory (ztta/roll_area - ztta/roll_first),4. Extended Memory (ztta/roll_extension(_nondia)).In the case of dialog work processes, the allocation sequence remains unchangedfrom that used in the MAP implementation:1. Roll memory (ztta/roll_first),2. Extended Memory (ztta/roll_extension(_dia)),

Activity (28)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
buddy261 liked this
Tanmayfico liked this
edy_suranta liked this
Claudiu Jucșor liked this
Trp Coolhunk liked this
swayam liked this
.doc liked this
yawerak liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->