>>Why the work process goes into PRIV mode.
because the transaction executed allocates more than ztta/roll_extension extended memory or on Windows 32 bit more than the addressable extended memory.
If a transaction has only allocated extended memory it can be moved between the work processes.
if it need more memory the memory is allocated exclusive to a work process and the transaction can no longer switch to a different work process. Thus the work process gets PRIVate to the transaction. The work process is released again after the transactions has been ended.
>>How to prevent this situation in advance.
well, in theory you can set the abap/heap_area_* parameters to 0 but I doubt that all your transactions will still work after that.
there are always some transactions running into PRIV mode.
The question that remains: is it necessary that they need to allocate so much memory. The answer has to be given by the transaction designers.
>>waht are post processing actions to be done?
This depends on the transaction running. Normaly no post processing actions should be necessary. But you should contact those who where running them.
regards
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.