RE: Workprocess in PRIV mode

Hi all,
We are facing problem in SAP. The performance of the system is very low and all the dialog workprocess are entering 'PRIV' mode in 'ONHOLD' state.
Can you please say me what are the possible reasons for process to enter 'PRIV' mode?
Thanks in advance
Regards,
Sowmya K

Hi,
If all the work processes are going in the PRIV mode, it is very possible to be Kernel bug which you can check with SAP.
Understanding the HEAP memory better, If a dialog work process has used up the roll area assigned to it and the extended memory, private memory is assigned to the work process. The work process goes into PRIV mode (private).
In the parameter settings, ensure that not too many dialog work processes are simultaneously in the PRIV mode, since this lowers system performance.
The other Work Process types (background, update, enqueue and spool work processes) are assigned heap memory after the roll area is used up. Allocating Extended Memory is not useful since no context change occurs for these processes.
Other processes cannot use private (heap) memory. After releasing the assigned memory, the operating system still considers the (virtual) memory as being occupied by the allocating process. These characteristics of heap memory require that:
1. The work process can be run in PRIV mode (private) when the local memory is assigned. This means that the work process is reserved for processing the current user context until the context releases the work process again when the request has ended.
2. The work process, if it has used a lot of private memory, is restarted when the user context is terminated and the local memory is returned. The restart makes the local memory available again for other processes. A restart occurs if a work process uses more local memory than is defined in the parameter abap/heaplimit. The mechanism is displayed again there.
Automatic Termination of PRIV Mode Processes:
If too many dialog work processes run in the PRIV mode in an SAP application server, performance problems arise. The normal processing of user inquiries is slowed down by the PRIV mode work processes.
The SAP System offers a mechanism that lets you terminate non-active dialog processes in the PRIV mode. This mechanism helps reduce performance problems.
The mechanism works as follows:
In the PRIV mode, a maximum number (n) of dialog work processes can run without any time restrictions.
To determine this number n, set the value of the profile parameter rdisp/wppriv_max_no. If a value is not entered, the SAP System determines this number using the following formula:
the number (n) is set to the greater of the 2 following values:
Number of dialog work processes minus 5
1
If more than (n) dialog work processes are active and the time span set in parameter rdisp/max_priv_time (default 600 seconds) has elapsed, the transaction for that PRIV process, which has spent the longest possible time in PRIV mode, is reset.
Hope this information helps in sorting out the issue.
Thanks
Tanuj
(*Award point if useful.)

Similar Messages

Stop DIA work process with PRIV mode.

Hi,
How to stop DIA workprocess with PRIV mode. by searching notes, I find it is possible to setl the max time and max number of the private memory.
Kind regards,
Masaaki

Hello Masaaki,
Before deciding whether to wait for the process to finish by itself or not, i would suggest that you find out the program which is causing the work process to go into PRIV mode. Once this is done, as your technical guys (ABAP) to analyse why this is happening (is the program logic inefficient and hence using so much memory etc).
You have to note that (Dialog) work processes going into PRIV mode is not a healthy sign for the SAP application server.
This is beacuse once the WP goes into PRIV mode it is not available to any other transactions, and we only have a limited number of work processes.
Please make sure the parameters below are defined in RZ10 instance profile:
rdisp/max_priv_time - used to define the maximum time that a work process can remain in PRIV mode. (After this the work processes is terminated and restarted). This is reasonable because beyond the time limit set, it is imperative to assume that the program using the work process is in efficient. (in case a program really needs that much time, it needs to be scheduled as a background job).
rdisp/wppriv_max_no- this parameter defines the maximum number of work processes that can be in PRIV mode. Very useful.
Also, make sure that a parameter ABAP/heaplimit is defined. This ensures that if a program eats up a certain amount of heap memory, the work process being used can be terminated.
And finally please do check if your extended memory allocation is not big enough. the parameter em/initial_size_mb defines the fixed size of extended memory. Increasing this size only if you find that a lot of processes are frequently going into PRIV mode.
Hope this helps.
Regards,
Prashant

Workprocess are stopped due to PRIV mode

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

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>

Dialogue workprocesses going in PRIV mode

Dear all,
More than 95% of dialogue work processes are going in PRIV mode
The extended memory in ST02 is 100% full
Nobody is able to do nothing
Below pasted are the values from the instance profile
ztta/roll_extension                           4000000000
rdisp/wppriv_max_no                         1
zcsa/db_max_buftab                          10000
sap/bufdir_entries                          6000
rsdb/obj/large_object_size                  16384
rsdb/obj/max_objects                        4000
rsdb/obj/buffersize                         8192
rsdb/ntab/irbdsize                          9000
rsdb/ntab/ftabsize                          45000
rsdb/ntab/entrycount                        30000
rsdb/cua/buffersize                         6000
abap/buffersize                             600000
zcsa/presentation_buffer_area               6600000
zcsa/table_buffer_area                      30000000
ztta/parameter_area                         8000
auth/auth_number_in_userbuffer              9000
Any suggestions?

Dear all,
Problem was with the following two parameters: --
em/initial_size_MB = 512
em/max_size_MB = 512
De-activating these 2 parameters in instance profile, solved the problem
Thank you all
Would like to add some more here just in case if anyone wants some more details: --
If a Dialog work process has used its quota of Extended Memory (EM) defined by parameter ztta/roll_extension OR all EM has been used up by all the other work processes (em/initial_size_MB), then the task starts to allocate HEAP up to quota (per work process) of abap/heap_area_dia.(this is PRIV mode).
To investigate, check out the dev_w* trace file, to check which program cause work process go into PRIV
Also, follow what Markus has suggested
You can try to set rdisp/wppriv_max_no to prevent this kind problem.
Exmaple: If you set it as 5, will limit only 5 work processes go to PRIVmode.
Please also update your kernel patch to latest version, if you haven't done so.
See also note: 79435 Automatic resetting from PRIV mode
Rgds

Workprocess in Private Mode

Hi,
In our BI system, we want to avoid that dialog workprocess entering in private mode.
Now we have the next situations:
Number of dialog workprocess: 30
rdisp/wppriv_max_no: 25
rdisp/max_priv_time: 600
We had thought to change this parameters to:
rdisp/wppriv_max_no: 15
rdisp/max_priv_time: 3600
Do you think these new parameters are correct or that we can to have some problems whit them?.
Best Regards

Hello Maximino,
as so often: It depends.
And as I wrote: You can't really compare these two scenarios.
The new setting could result in this:
20 work processes in priv mode since about 45 minutes.
20 other work processes in priv mode since about 30 minutes.
All the other work processes in priv mode since about 15 minutes.
So nobody else will be allowed to work. This will only change in 15 minutes, when those exceeding 60 minutes will be cancelled.
On the other hand, if know know for sure that only a few of your users will go priv, your suggestion will work.
There are a lot of SAP notes or help texts about priv mode. You might want to look for different solutions. Or it might be necessary to buy more memory for your SAP server.
regards

Proccesses goes to PRIV mode

Hi, we have problem with proccesses going to PRIV mode (SAPHTTP), extended memory:
Roll, extended and heap memory EXTM
ztta/roll_area                3000000    Byte Roll area per workprocess (total)
ztta/roll_first               1          Byte First amount of roll area used in a dialog WP
ztta/short_area               1600000    Byte Short area per workprocess
rdisp/ROLL_SHM                16384      8 kB Part of roll file in shared memory
rdisp/PG_SHM                  8192       8 kB Part of paging file in shared memory
rdisp/PG_LOCAL                150        8 kB Paging buffer per workprocess
em/initial_size_MB            4092       MB    Initial size of extended memory
em/blocksize_KB               4096       kB    Size of one extended memory block
em/address_space_MB           4092       MB    Address space reserved for ext. mem. (NT only)
ztta/roll_extension           2000000000 Byte Max. extended mem. per session (external mode)
abap/heap_area_dia            2000000000 Byte Max. heap memory for dialog workprocesses
abap/heap_area_nondia         2000000000 Byte Max. heap memory for non-dialog workprocesses
abap/heap_area_total          2000000000 Byte Max. usable heap memory
abap/heaplimit                40000000   Byte Workprocess restart limit of heap memory
abap/use_paging               0                Paging for flat tables used (1) or not (0)
have You any advice?
Thanks

Hi,
A process going into PRIV means that either it has exhausted its quota of extended memory (ztta/roll_extension) or that the total extended memory (em/initial_size_MB) has been used up by other sessions.
The parameters look pretty standard, but you must determine the memory usage at the time you see a PRIV process. Do this via SM04 -> Goto -> Memory.
Another piece of advice: when you ask a question about memory-related issues, please always mention your operating system (Windows, UNIX, Linux, ...), O/S release and SAP release. SAP memory management has quite a few platform dependencies in it.
Regards,
Mark

Stop DIA work process with PRIV mode in my program

Hello,
I write Program that display in the end an alv report and when i display it after same time my dia wp get in PRIV mode
I search about it and I didn't find the solution but it happend only with my program this reject the memory parameter that cause the problem
Thanks for your help

Hi,
>I think this not the problem because in the dev and the qa system it won't get in priv thanks
>mode and the have the same value in the parameter ztta/roll_extension and the qa is the copy of the prod but 3 month old
And these 3 months difference can perfectly explain why you have the problemn on production and not on QA.
Private modes are generated usually because of badly designed programs (including standard ones...).
ALV is not designed to display a huge amoiunt of data.
Beware also of internal tables : Abap programmer usually abuse internal tables thinking memory is an unlmimited ressource...
Just a few ideas.
Regards,
Olivier

WP are going to priv mode

Hi Gurus,
WP's are going to priv mode. user is not accepting to kill the process or reduce the number of records. what is the best way to do as a basis consultant?
Thanks in advance.

Dear Sahad,
<PRIV> mode will be used if the work process starts to allocate heap - or private,
thus PRIV - memory. This is not necessarily a bad thing. There are two scenarios
that may lead to such a system state:
1. There is a small number of users that create huge contexts. In this case, it
will be OK to have such users allocate memory from heap and exclusively lock
a work process for them (this is a side-effect of the PRIV state, as heap memory
content can not be seen by another process, and the user context can no longer
be 'rolled' into another work process. The limit when this will happen is either given
by the ressource limit (em/initial_size_MB, EM/TOTAL_SIZE_MB) which is the
overall amount of extended memory (EM). EM is a shared memory. The other limit
is a user specific quota given by ztta/roll_extension (or ES/SHM_MAX_PRIV_SEGS
for AIX, when ES/TABLE=SHM_SEGS is used). As I said, this is normally OK, and
a small number of PRIV processes is not a problem at all.
2. The user contexts are equally big, but there is not enough EM available on the
instance. This will force EVERY user context into PRIV, as soon as the EM is
exhausted. The fact that EM is exhausted will be seen in transaction ST02 (look
for SAP Memory, Extended memory). Also check with transaction SM04, Goto,
Memory, the size of the user contexts. In this case, increasing EM, or reducing the
amount of users on the instance are your choices.
As I said, if this is only one or two work processes, you must not worry about them.
Best Regards,
Tim

OS paging versus PRIV mode

Hi Experts,
We always found there are users using more than 2GB for transaction, so we did the below changes in our system to avoid fragmentation and paging of extended memory
1.Instead of allowing a process to grab 2 GB of (shared) extended memory before going in PRIV mode, the limit will be reduced to 800 MB.As a counterpart, private heap memory limits will be increased from 2 GB to 3,2 GB.
2.So total maximum memory per user is still 4 GB, but high memory users will have to "pay for it"
3. The advantage is that private memory is given back to the operating system once the transaction is finished, whereas shared extended memory is never given back (by design).
our assumption is we would never see MaxUse of extended memory > 12 GB in future.so users are allowed getting PRIV mode from time to time in our production.
But now we are getting some other problem.We are getting too much OS paging (according SE06)
Just what to confirm here with the experts
1. This PRIV mode of the WP uses the needed memory exclusively, the WP will not be interrupted and so uses much CPU, so Priv mode causes the high OS paging.?
2. Does SE06 includes the OS paging with IO?
3. What are the other options we do have to reduce this high paging
Please guide
Thanks,
Jansi

1. This PRIV mode of the WP uses the needed memory exclusively, the WP will not be interrupted and so uses much CPU, so Priv mode causes the high OS paging.?
    PRIV mode or not, paging will occur if there is not enough memory. Even in PRIV mode, WP will be interrupted at O/S level if O/S follows round-robin method(UNIX) of assigning tasks to CPU.
2. Does SE06 includes the OS paging with IO? I assume yes.
3. What are the other options we do have to reduce this high paging
Here are options:
   1) Tune ABAP programs.
   2) Add more memory. How much (AVG)free/min/max memory you see every hour in st06? If you see really low memory almost every hour every day, then I would either try to add more memory or tune ABAP programs or review memory allocation to different components(DB/SAP system(s)/Any other application/Java if dual stack) more carefully and revise allocation if needed or perform all of the above.
Bala

Workprocesses go into PRIV immediately

Our users connect through our intranet and a portal to a SRM backed (among other things). When a user starts a session from the intranet, we can see it using a dialog process at the backend. This dialog process starts in PRIV mode immediately. As a consequence, the process is linked to the user for the duration of the transaction. This happens to more than one user simultaneously, so the available dialog processes are saturated quickly and new sessions started from the intranet are no longer processed.
While executing the transaction at the backend (mostly BBPSC02), we also see processes with status "GUI", when a search of some sort is started. These sessions are not detected by the cleanup mechanism using rdisp/wppriv_max_no and rdisp/max_priv_time.
Has anybody seen this behaviour before?

Our users connect through our intranet and a portal to a SRM backed (among other things). When a user starts a session from the intranet, we can see it using a dialog process at the backend. This dialog process starts in PRIV mode immediately. As a consequence, the process is linked to the user for the duration of the transaction. This happens to more than one user simultaneously, so the available dialog processes are saturated quickly and new sessions started from the intranet are no longer processed.
While executing the transaction at the backend (mostly BBPSC02), we also see processes with status "GUI", when a search of some sort is started. These sessions are not detected by the cleanup mechanism using rdisp/wppriv_max_no and rdisp/max_priv_time.
Has anybody seen this behaviour before?

Status Hold in SM50 reason Private mode

Dear all,
BIP PROD system , one of the work process got status shows hold (Reason private mode)
3    DIA     12699     On Hold     PRIV     Yes     1               11070     SAPMSSY1     400     MASOND
In SM04 i have checked that particular user , i got below details .
400     MASOND     0200-00020     SESSION_MANAGER     14.25.41     1     GUI     0
No Transaction                          Time
1   Session Manager Menu Tree Display    14:25:41
i have checked trace file in SM50 its shows below details log of that particular WP.
last few lines of Trace Data: dbcipwp_BWP_02dev_w3 :
M Mon May 2 09:31:56 2011
M
M *****************************************************************************
M *
M * LOCATION    SAP-Server ap01jrp_JRP_20 on host ap01jrp (wp 6)
M * ERROR       Warning: EM-Memory exhausted: Workprocess gets PRIV
M *
M * TIME        Mon May 2 09:31:56 2011
M * RELEASE     700
M * COMPONENT   EM
M * VERSION     37
M * RC          7
M * MODULE      emxx.c
M * LINE        1897
M * COUNTER     274285
M *
M *****************************************************************************
M
S
S Mon May 2 09:34:25 2011
S found spool memory service RSPO-ACTIONS at c000000083446750
B table logging switched off for all clients
C build_stmt: reallocating stmt buffer: 2000 -> 3002 characters
B
B Mon May 2 09:41:26 2011
B create_con (con_name=R/3*TIMESTAMP)
B New connection 2 created
B Mon May 2 09:41:30 2011
B create_con (con_name=R/3*WB)
B New connection 3 created
B
B Mon May 2 09:41:39 2011
B create_con (con_name=R/3*)
B New connection 4 created
C
C Mon May 2 10:16:07 2011
C Disconnecting from connection 1 ...
C Closing user session (con_hdl=1,svchp=6000000002fbc578,usrhp=6000000002fbbfe8)
C Now I'm disconnected from ORACLE
B Disconnected from connection con_da={R/3*,1028657,4}
C
C Mon May 2 10:16:56 2011
C application info callback registered
C Client NLS setting (OCINlsGetInfo): connection handle 1 -> 'AMERICAN_AMERICA.WE8DEC'
C Logon as OPS$-user to get SAPR3's password
C Connecting as /@BWP on connection 1 (nls_hdl 0) ... (dbsl 701 220409)
C Nls CharacterSet                 NationalCharSet                   EnvHp      ErrHp ErrHpBatch

Contiune of log details :
C    0 WE8DEC                                                    60000000028940c0 600000000289ba40 600000000289f428
C Starting user session: OCISessionBegin(con_hdl=1, usr='/',svchp=60000000030a5a18, srvhp=60000000028a16a8, usrhp=6000000003ce5ae8)
C Now '/@BWP' is connected: con_hdl=1, nls_hdl=0, session_id=132.
C Got SAPR3's password from OPS$-user
C Disconnecting from connection 1 ...
C Closing user session (con_hdl=1,svchp=60000000030a5a18,usrhp=6000000003ce5ae8)
C Now I'm disconnected from ORACLE
C Connecting as SAPR3/<pwd>@BWP on connection 1 (nls_hdl 0) ... (dbsl 701 220409)
C Nls CharacterSet                 NationalCharSet                   EnvHp      ErrHp ErrHpBatch
C    0 WE8DEC                                                    60000000028940c0 600000000289ba40 600000000289f428
C Starting user session: OCISessionBegin(con_hdl=1, usr=SAPR3/<pwd>, svchp=60000000030a5a18, srvhp=60000000028a16a8, usrhp=60000000
C Now 'SAPR3/<pwd>@BWP' is connected: con_hdl=1, nls_hdl=0, session_id=132.
C DB instance BWP is running on dee with ORACLE version 10.2.0.4.0 since DEC 12, 2010, 19:35:29
B Connection 1 opened (DBSL handle 1)
B Wp Hdl ConName                        ConId     ConState     TX HC PRM RCT FRC TIM MAX OPT Date     Time   DBHost
B 003 000 R/3                            000000000 ACTIVE       NO NO YES NO NO 000 255 255 20110502 091949 dee
B 003 001 R/3*BWMON                      003014083 ACTIVE       NO NO NO NO NO 004 255 255 20110502 101656 dee
B 003 002 R/3*TIMESTAMP                  003014075 DISCONNECTED NO NO NO NO NO 004 255 255 20110502 095141 dee
B 003 003 R/3*WB                         003014076 DISCONNECTED NO NO NO NO NO 004 255 255 20110502 095212 dee
B 003 004 R/3*                           001028657 DISCONNECTED NO NO NO NO NO 000 255 255 20110502 101607 dee
C
C Mon May 2 10:16:58 2011
C build_stmt: reallocating stmt buffer: 3328 -> 4329 characters
C build_stmt: reallocating stmt buffer: 4329 -> 5331 characters
C
C Mon May 2 10:17:06 2011
C build_stmt: reallocating stmt buffer: 1792 -> 2798 characters
C build_stmt: reallocating stmt buffer: 2798 -> 3800 characters
M
M Mon May 2 10:18:17 2011
M *** WARNING => PfSetGuiTime: gui time too large, discard (gui=1319609000/resptime=0)
A
A Mon May 2 10:25:35 2011
A WP has reached abap/heaplimit = 40000000 bytes
C
C Mon May 2 10:41:07 2011
C Disconnecting from connection 1 ...
C Closing user session (con_hdl=1,svchp=60000000030a5a18,usrhp=6000000003ce5ae8)
C Now I'm disconnected from ORACLE
B Disconnected from connection con_da={R/3*,3014086,4}
C
C Mon May 2 14:23:21 2011
C application info callback registered
C Client NLS setting (OCINlsGetInfo): connection handle 1 -> 'AMERICAN_AMERICA.WE8DEC'
C Logon as OPS$-user to get SAPR3's password

Workprocess in hold

Hi guys,
In R/3 systems(4.7 with SQL) when i saw workprocess in SM50 which are in PRIV mode with Hold status but i saw same workprocesses in SM66 they are same PRIV mode but with stopped status.
why same workprocesses are showing different status in different SM50 and SM66.
any body know reason please let me know...
regards,
Pulla Rao

stoped/hold statuses means process is waiting for samething
(for example OS), there is a good explanation on each state in SM50/SM66, by pressing F1 on the process mode,
The status of hold in SM66 is equivalence to status stopped in SM50.
please notice that user that got to PRIV mode,
means he took quite a lot of memory,
the the WAS can not release the memory (by doing roll-out),
untill the user would leave the transaction
that's the reason why users, who get to PRIV, gets the meesage "please leave transaction before taking a brake"

Extended memory 50% free,but work process reach PRIV

hi,
many dialog work process reach PRIV mode though extended memory is 50% free.
profile parameters as below :
ztta/roll_first     1 MB
ztta/roll_extension     2GB
ztta/roll_area     6MB
abap/heap_area_dia     2GB
can anyone throw light ?

Hi Krishna,
In addition to the parameter you have mentioned check these parameter as well in the system.
A process going into PRIV means that either it has exhausted its quota of extended memory (ztta/roll_extension) or that the total extended memory (em/initial_size_MB) has been used up by other sessions.So increase these 2 parameter to start with and then tune others.
rdisp/ROLL_SHM                32768       8 kB Part of roll file in shared memory
rdisp/PG_SHM                  16384       8 kB Part of paging file in shared memory
rdisp/PG_LOCAL                150         8 kB Paging buffer per workprocess
em/initial_size_MB            61440       MB    Initial size of extended memory
em/blocksize_KB               4096        kB    Size of one extended memory block
em/address_space_MB           4096        MB    Address space reserved for ext. mem. (NT only)
ztta/roll_extension           2000000000 Byte Max. extended mem. per session (external mode)
abap/heap_area_total          64424500000 Byte Max. usable heap memory
abap/heaplimit                40000000    Byte Workprocess restart limit of heap memory
Also,consider setting rdisp/wppriv_max_no and rdisp/max_priv_time,so that system performance is not much impacted.
http://help.sap.com/saphelp_nw04/helpdata/en/7a/caa6f3bfdb11d188b30000e83539c3/content.htm
Regards,
Ashutosh

Is heap memory is particular for a workprocess?and extended memory too?

Is heap memory is particular for a workprocess?and extended memory too?
All the while I need to know is :is more than one workprocess can be in Priv mode?

Yes - heap is workprocess exclusive memory.
Extended memory is shared on the instance.
Yes - more than one WP can go to PRIV mode.
Markus

Does back ground jobs work process go to private mode or not

Hi Experts,
Can any one tell me
Does back ground jobs work process go to private mode or not
Thanks and Regards
Dan !!

Hi Dan,
I do not think background work processes would go into PRIV mode.
the orginal information was remove by Admin because provided by Cut and Paste from SAP Online Help.
you will find it <a href="http://help.sap.com/saphelp_47x200/helpdata/en/7a/caa6f3bfdb11d188b30000e83539c3/frameset.htm">here</a>
The distribution, participation in distributing or otherwise sending of this material is against the law. The material you are requesting is copyrighted material and available ONLY to customers of SAP. If you need such documents from the SAP Service Marketplace then you must have "S" user ID and login yourself to retrieve this material. If you do not have a "S" user ID then you should contact your own internal company groups responsible and request one or request them to retrieve the document for you.
By participating and sending such documents you are at risk for legal action and a removal of your account here on SDN and BPX.
DO NOT send material via email such as this! Further actions will result in officials within your company and your SAP Sales Account being notified and could result in legal action against you as an individual.

RE: Workprocess in PRIV mode

Similar Messages

Maybe you are looking for