Memory Management
Parameters-:
MEMORY ALLOCATION-:
Memory allocation sequence to dialog work processes in SAP. This article answers the following questions-:
Memory allocation sequence to Dialog work process in SAP
Usually ztta/roll_first is set to 1 in SAP, so that only technically necessary amount is allocated to roll memory. If the memory from the initial roll area [ztta/roll_first] is not sufficient for the user context then,
2. Extended memory is used until the extended memory is full or until the user quota is reached.
Extended memory is defined by the SAP parameter “em/initial_size_MB” and the user quota for dialog work process is defined by the parameter “ztta/roll_extension_dia”. If this memory is not sufficient then,
3. The rest of the roll area is used. This roll area is defined by SAP parameter “ztta/roll_area _ ztta/roll_first”
4. The system is forced to use local heap memory [private memory]. Then the work process goes into PRIV mode.
HEAP MEMORY is available until one of the following occurs-:
The work process cannot be terminated by the parameter “rdisp/max_wprun_time” [PRIV] when a work process enters PRIV mode, it remains connected to the user until the user ends the transactions or it is timed out by the system due to the memory or explicitly logged out using SM04/DPMON.
Question-: Users complain that they could not access the system [globally] users are encountering the hour glass mode, SM50/SM66/SM21 are not accessible.
Restrict the processes that goes into wp PRIV mode by using parameter “rdisp/wppriv_max_no=1 or 2”
rdisp/max_priv_time=60 secs to terminate the processes that are in PRIV mode.
NOTE-: The long memory programs/ transactions can be split into Variants (monthly) and schedule to run the background during off peak hours.
PHYS_MEMSIZE=2GB
Task manager in Window
If the memory is not released then we use command “ipcrm” or use “cleanipc” to release the memory blocked at OS level.
LOGGING
TRACING
These are explicitly switched on the system to trace/track either a user missing authorization, en queue issues, rfc issues, sql issues, kernel issues etc.
EXECUTE ST01
Select the trace and switch on. Specify the user, process etc
Can refer to different SAP Notes for more detailed information.
Regards
Samar :smile:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
3 | |
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 |