WORK PROCESS GO INTO PRIV MODE

[Former Member]

Hi every body,

All work processes of the SAP System go into the PRIV mode after some time This soon causes long waiting times for all other users,

SAP configuration 4.70 , Oracle 9.2.0.4, 40GB RAM , 6 CPU

kernel release 640

kernel make variant 640_REL

compiled on AIX 1 5 00538A4A4C00

compiled for 64 BIT

compilation mode Non-Unicode

compile time Jul 16 2006 20:40:53

update level 0

patch number 139

source id 0.139

-

---

supported environment

-

---

database (SAP, table SVERS) 610

620

630

640

operating system

AIX 2 5

My parameters profils:

login/fails_to_user_lock = 5

#parameter created by: DEVALLER 02.08.2006 11:17:44

rdisp/PG_SHM = 16384

#parameter created by: DEVALLER 02.08.2006 11:16:52

#old_value: 6500000

#old_value: 7500000

#old_value: 8000000 changed:

DEVALLER 24.03.2007 11:54:16

ztta/roll_area = 8500000

#parameter created by: DEVALLER 01.06.2005 09:56:08

abap/fieldexit = yes

#parameter created by: DEVALLER 23.05.2005 17:23:13

rdisp/gui_auto_logout = 7200

#parameter created by: DEVALLER 22.03.2005 10:03:52

gw/max_sys = 2000

#parameter created by: DEVALLER 22.03.2005 10:03:13

gw/max_overflow_size = 25000000

#parameter created by: DEVALLER 22.03.2005 10:02:37

rdisp/max_comm_entries = 2000

#parameter created by: DEVALLER 22.03.2005 10:02:08

rdisp/tm_max_no = 2000

#parameter created by: DEVALLER 22.03.2005 10:01:31

gw/max_conn = 2000

#parameter created by: DEVALLER 22.03.2005 10:00:50

rdisp/appc_ca_blk_no = 2000

#parameter created by: DEVALLER 22.03.2005 10:00:17

rdisp/wp_ca_blk_no = 1000

#parameter created by: DEVALLER 22.03.2005 09:59:00

#old_value: 14592

#old_value: 7168

#old_value: 8192

EM/TOTAL_SIZE_MB = 7168

#parameter created by: DEVALLER 13.12.2004 11:32:31

#old_value: 3000

#old_value: 20000

#old_value: 25000

#old_value: 30000

rsdb/obj/max_objects = 35000

#parameter created by: DEVALLER 13.11.2004 11:55:02

gw/netstat_once = 0

#parameter created by: DEVALLER 08.11.2004 10:59:09

#old_value: 10000

#old_value: 4000

#old_value: 5000

#old_value: 8000

rsdb/ntab/irbdsize = 9000

#parameter created by: DEVALLER 08.11.2004 10:58:35

#old_value: 40000

#old_value: 45000

#old_value: 60000

rsdb/ntab/ftabsize = 62000

#parameter created by: CAIAZZAM 10.07.2007 14:43:00

login/min_password_lng = 8

#

#

#

login/password_expiration_time = 180

#parameter created by: SAP* 01.04.2004 15:29:19

login/system_client = 300

SAPSYSTEMNAME = PRD

INSTANCE_NAME = DVEBMGS00

SAPSYSTEM = 00

#old_value: 10

#old_value: 12

#old_value: 14

#old_value: 16

rdisp/wp_no_dia = 20

rdisp/wp_no_vb = 5

#old_value: 2

#old_value: 4

#old_value: 3

rdisp/wp_no_vb2 = 4

rdisp/wp_no_enq = 1

#old_value: 6

#old_value: 5

rdisp/wp_no_btc = 7

#old_value: 1

#old_value: 2

rdisp/wp_no_spo = 3

#old_value: E changed: SAP* 01.04.2004 15:29:00

DEVALLER 06.11.2004 10:40:41

zcsa/system_language = I

1. rslg/send_daemon/listen_port - Log Sender Listen Port

rslg/send_daemon/listen_port = 3700

#parameter created by: DEVALLER 06.11.2004 10:32:56

zcsa/installed_languages = DEI

#parameter created by: DEVALLER 22.03.2005 09:57:26

em/global_area_MB = 50

#parameter created by: DEVALLER 22.03.2005 10:06:23

rsdb/max_blocking_factor = 5

#parameter created by: DEVALLER 22.03.2005 10:05:29

#old_value: 10000

#old_value: 20000

enque/table_size = 25000

#parameter created by: DEVALLER 22.03.2005 09:56:29

#old_value: 20000

#old_value: 30000

#old_value: 35000

rsdb/obj/buffersize = 40000

#parameter created by: DEVALLER 22.03.2005 09:55:52

#old_value: 10000

#old_value: 11000

DEVALLER 24.03.2007 11:52:44

sap/bufdir_entries = 13000

#parameter created by: DEVALLER 05.06.2005 20:07:27

DIR_ORAHOME = /oracle/PRD/920_64

#parameter created by: DEVALLER 02.08.2006 11:34:19

rdisp/max_arq = 2000

#parameter created by: DEVALLER 02.08.2006 11:33:26

ES/SHM_SEG_COUNT = 4096

1. rslg/send_daemon/talk_port - Log Sender Talk Port

rslg/send_daemon/talk_port = 1300

1. abap/heap_area_dia - Limit of heap per Emode on Dialogprozesses

#old_value: 180000000

: RENATO 11.02.2007 10:11:25

DEVALLER 25.04.2007 08:29:59

DEVALLER 03.05.2007 10:36:16

DEVALLER 03.05.2007 10:40:26

abap/heap_area_dia = 300000000

1. abap/heap_area_nondia - Limit of heap per Emode on Batch or VB or Spool

#old_value: 180000000 changed: SAP* 01.04.2004 15:28:44

#old_value: 400000000

: RENATO 11.02.2007 10:11:25

DEVALLER 25.04.2007 08:29:59

DEVALLER 03.05.2007 10:36:16

DEVALLER 03.05.2007 10:40:26

abap/heap_area_nondia = 300000000

1. abap/buffersize - Program Buffer Size

#old_value: 200000 changed: DEVALLER 07.06.2004 16:33:08

#old_value: 400000

#old_value: 450000

#old_value: 500000

#old_value: 520000

#old_value: 550000

#old_value: 650000

DEVALLER 24.03.2007 11:52:44

abap/buffersize = 750000

1. rsdb/cua/buffersize - Size of CUA Buffer

#old_value: 5000

#old_value: 10000

rsdb/cua/buffersize = 20000

1. zcsa/presentation_buffer_area - Size of the buffer allocated for screens (Dynp

#old_value: 20000000

#old_value: 25000000

#old_value: 30000000

#old_value: 35000000

#old_value: 38000000

zcsa/presentation_buffer_area = 40000000

1. zcsa/table_buffer_area - Size of Resident-Table Buffer

#old_value: 50000000

#old_value: 60000000

#old_value: 65000000

#old_value: 70000000

#old_value:

#70000000

1. 75000000

#changed: 29.06.2006 09:22:40

24.03.2007 11:52:44

zcsa/table_buffer_area = 76000000

1. zcsa/db_max_buftab - Directory Entries in Table Buffer

#old_value: 10000

#old_value: 15000

#old_value: 18000

DEVALLER 24.03.2007 11:52:44

zcsa/db_max_buftab = 20000

1. rtbb/buffer_length - Size of partial table bufferers

#old_value: 20000

rtbb/buffer_length = 30000

1. rtbb/max_tables - Number of Buffer Directory Entries

rtbb/max_tables = 500

1. ES/TABLE - Selection of ES implementation

ES/TABLE = SHM_SEGS

1. ES/SHM_MAX_PRIV_SEGS - Max segments for private context usage

#old_value: 2

#old_value: 63

ES/SHM_MAX_PRIV_SEGS = 3

1. ES/SHM_PROC_SEG_COUNT - Number of segments to use for each work process

#old_value: 5

#old_value: 64

ES/SHM_PROC_SEG_COUNT = 4

1. ES/SHM_SEG_SIZE - Segment size in Bytes

#ES/SHM_SEG_SIZE = 2048

DEVALLER 02.08.2006 11:18:38

ES/SHM_SEG_SIZE = 2048

1. em/max_size_MB - The maximum size of extended memory pool

em/max_size_MB = 4096

1. em/initial_size_MB - The initial size of extended memory pool

ed: SAP* 21.10.2007 13:43:47

em/initial_size_MB = 1024

#----

---

#Valori default SAP per dimensioni pool Shared Memory

#----

---

#parameter created

ipc/shm_psize_01 = -10

#parameter created

ipc/shm_psize_02 = -40

#parameter created

ipc/shm_psize_03 = -10

#parameter created

ipc/shm_psize_04 = -10

#parameter created

ipc/shm_psize_06 = -40

#parameter created

ipc/shm_psize_07 = -10

#parameter created

#old_value: 0

ipc/shm_psize_30 = -10

#parameter created

ipc/shm_psize_31 = -10

#parameter created

ipc/shm_psize_33 = -10

#parameter created

ipc/shm_psize_34 = -10

#parameter created

ipc/shm_psize_51 = -10

#parameter created

ipc/shm_psize_52 = -10

#parameter created

ipc/shm_psize_54 = -10

#parameter created

ipc/shm_psize_55 = -10

#parameter created

ipc/shm_psize_57 = -10

#parameter created

ES/SHM_USER_COUNT = 4096

#parameter created

ipc/shm_psize_58 = -10

#----

---

#Valori default SAP per dimensioni pool Shared Memory

#----

---

#parameter created

ipc/shm_psize_10 = 366000000

#parameter created

ipc/shm_psize_40 = 998000000

Help me , please

Thank You

CM

[tanuj_gupta · Accepted solution]

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.

<b>Automatic Termination of PRIV Mode Processes:</b>

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.

<u>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:</u>

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.

Award point if useful.

Thanks

Tanuj

[Former Member]

Question resolved.

thank You

[Former Member]

Is this a DB+CI instance?

I see that you have 40GB of physical memory available and your configured extended memory is not large enough. You use a kernel (640) where you can sacle-up your extended memory even above 32GB. So why u restrict to 7GB of extended memory ???

Increase your extended memory allocation and check ur swap space allocation is good enough.

/Manoj

[Former Member]

I'm sorry , my parameter abap/heap_area_dia or abap/heap_area_nondia is 300MB.

Thank you

[Former Member]

Hello Maurizio,

I rechecked the sap notes. The 80MB for abap/heap_area_dia or abap/heap_area_nondia is not recommanded anymore, if you have an 64bit system. You find most of the settings in note 789477.

You can set these parameters to 2GB. But first try to increase the ztta/roll_extentions. As long as the user is only using the ztta/roll_extention memory the workprocess doesn't go in the priv mode.

If you have set the ztta/roll_extension to 2GB or 4GB and your workprocess are still going in the priv mode, than you should ask the developers about the abap they are using. Often it is possible, that they can change the abap or reducing the select statement.

Regards,

alexander

[Former Member]

Hello Alexander,

EM/TOTAL_SIZE_MB is the same parameter EM/MAX_SIZE_MB?

Thank you.

[Former Member]

Hello Maurizio,

yes it is. I still don't now why the sap is using both parameters. If I remember correct one of the parameters help you to get the right information with sappfpar.

Regards,

Alexander

[Former Member]

Hi Maurizio,

In your case you should use EM/TOTAL_SIZE_MB (as of kernel 4.6D patch level 570) and I believe this is case sensitive parameter maintain this in CAPS. From your profile parameters it shows you have your extended memory configured only 7 GB. For me it looks far less.

Workprocesses go into PRIV mode in two conditions.

Case 1) When workprocess uses up it's extended memory quota(restricted by ztta/roll_extension paramter)

Case 2) When total extended memory(EM/TOTAL_SIZE_MB) is exhausted, in this case workprocesses go into PRIV mode though they have not reached their quota.

Since you indicated "ALL" work process going into PRIV mode, I assume this is due to Case 2, So increase EM/TOTAL_SIZE_MB. Recommendation on parameter value depends on physical RAM available in the server and swap space configured. If you are using 64 bit kernel refer to SAP note 445533 it may be useful.

Note - ensure that total memories configured for your applications running on server i.e. SAp + Oracle + AIX etc should be less than server available memory(RAM+Swap). Otherwise you may encounter signal 33 which causes instance to go down

Regards,

Sankar

[Former Member]

as of 4.6D patch level 570, em/max_size_MB is replaced by EM/TOTAL_SIZE_MB

[Former Member]

Hi,

please check the parameter should be ztta/roll_first = 1.

Regards

Ben

[Former Member]

Thank you Alexander for your feedback.

Do you have some additional information regarding point

abap/heap_area_dia or abap/heap_area_nondia (on aix 80MB)?

I can decrease 650MB to 80MB abap/heap_area_dia or abap/heap_area_nondia or both?

Thank you

[Former Member]

Hello,

I can't find the value for ztta/roll_extension. Please increase this parameter to 2GB. And if this isn't enough then try 4GB.

Users allocate in the following way the memory

ztta/roll_first (should be set to 1)

ztta/roll_area 6500000

ztta/rollextension = 2GB or 4GB or more

abap/heap_area_dia or abap/heap_area_nondia (on aix 80MB)

It is better to increase the ztta/rollextension and keep the heap small.

Also you can increase the value for

em/max_size_MB = 4096 to 16GB

ES/SHM_MAX_PRIV_SEGS = 3 to 7

ES/SHM_PROC_SEG_COUNT = 4 to 8

Regards,

Alexander