on 05-17-2008 6:32 AM
hi experts,
one of applicatin server most of the workprocess have been stopped due to reason PRIV mode. I killed the session of some users but the problem persisting again.
please suggest
regards,
Sudhakar K
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI
Ideally there should not be any work process running in the PRIV (or the PRIVATE ) mode as this consumes the shared system memory and affects the performance of the system. The work process in such a mode enters the HEAP memory of the user. Please refer to memory management for this as discussed above.
Also, if possible, please kill such a process with confirmations from the user.OR even better, ask the user himself to logout of the system and log back in.Such activities would release the memory resources occupied by such a WP
To kill such a process..Run SM66
Goto Edit Tab > Process>Restart after error --> yes (in case its No)
Then again Edit Tab --> Process --> cancel --> without core
Regards
Chen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
When a a WP enters in PRIV mode is because it is using Heap Memory, as this memory is shared the WP must finish its process so the memory can be cleared. The problem is that either Extended memory is not enough or the program takes too much memory, if the problem happens in any standard program then you should define more Extended memory, if the problem only happens during customized programs then the problem is surely a programing error.
Good luck
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sudhakar,
Have a look at the following link, it will explain you about memory management
http://help.sap.com/saphelp_45b/helpdata/en/02/9625e3538111d1891b0000e8322f96/frameset.htm
Hope this helps you a lot.
Cheers,
Praveen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please check the memory parameters like ,
abap/heap_area_dia
abap/heap_area_nondia
abap/heap_area_total
abap/heaplimit
and check the recommendations ( RZ11 ) and increase to 2000000000 (UNIX) if u have high memory requirements and more concurrent users doing heavy tasks.
These thresholds can be determined with
the test program 'memlimits'
cwrci:cwradm 5> memlimits
SAP R/3 address space configuration test tool V3.2 (98/01/14)
=========================================================================
Restart, set early swap allocation (PSALLOC=early)
SAP R/3 address space configuration test tool V3.2 (98/01/14)
=========================================================================
Check the maximum data size per process (malloc)
Check the available swap space (malloc in several processes)
Process 1974488 allocating ... Size = 4096MB Total: 4096MB
Upper size limit 4096 reached. Finish checking
Total available swap space = 4096MB
Check the maximum size of mapped file (mmap anonymous,dev/zero)
Check protection operations on this area (protect)
Trying to mmap 512MB ... successfull
Trying to mmap 768MB ... successfull
Trying to mmap 1024MB ... successfull
Trying to mmap 1280MB ... successfull
Trying to mmap 1536MB ... successfull
Trying to mmap 1792MB ... successfull
Trying to mmap 2048MB ... successfull
Trying to mmap 2304MB ... successfull
Trying to mmap 2560MB ... successfull
Trying to mmap 2816MB ... successfull
Trying to mmap 3072MB ... successfull
Trying to mmap 3328MB ... successfull
Trying to mmap 3584MB ... successfull
Trying to mmap 3840MB ... successfull
Trying to mmap 4096MB ... successfull
Upper size limit 4096 reached. Finish checking
Trying to mprotect 4096MB ... successfull
Maximum mapped file size: 4096MB
Maximum mprotect size: 4096MB
R/3 parameter em/initial_size_MB up to 4096 permitted
Check the maximum address space per process usable
both by process local memory and mapped file
Maximum address space ( mmap(4096 MB)+ malloc(1676MB) 😞 5772MB
----
Result |
----
Maximum heap size per process........: 4096 MB
measurement limited to 4096 MB
this value is probably limited by swap space
Maximum mapped file size (mmap)......: 4096 MB
measurement limited to 4096 MB
Maximum protectable size (mprotect)..: 4096 MB
measurement limited to 4096 MB
em/initial_size_MB > 4096 MB will not work
Maximum address space per process....: 5772 MB
Total available swap space...........: 4096 MB
measurement limited to 4096 MB
main memory size x 3 recommended , minimum 1 GB
cwrci:cwradm 6>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In SM50 select each work process with PRIV, make sure restart after error is enabled and then cancel each process without core. This will basically restart the work process and work process PRIV mode will be gone. The reason it is in PRIV mode is because some user muste have used heam memory of thw work process. There fore until that memory is cleared, the work process will only server that user only. By canceling and restarting the process you create the heap
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.