DIA work processes in PRIV status

[Former Member]

Hello,

I understand that DIA work processes going in PRIV mode indicates memory issues and we need to work on setting up memory parameters. However, my question here is that it was working fine till yesterday and since today morning all or most DIA work processes are going in PRIV mode. Even when DIA work processes if freed up and occupied by new user only for 20 seconds then also it goes in PRIV status.

Can anyone please assist on what could be the main reason for this sudden behavior for one of the app server? I will work on setting up memory parameters in parallel.

2	DIA	242158	On Hold	PRIV	Yes	7			11	RFITEMAR	300	1673
3	DIA	622850	On Hold	PRIV	Yes	1			1	RM06EN00	300	1019
4	DIA	794938	On Hold	PRIV	Yes	2			89	SAPMV45A	300	1080
5	DIA	549146	On Hold	PRIV	Yes	1			178	SAPLMIGO	300	5353
8	DIA	639392	On Hold	PRIV	Yes	7			89	RFITEMAP	300	4044
9	DIA	364980	On Hold	PRIV	Yes				103	SAPLSMTR_NAVIGATION	300	5393
12	DIA	569660	Waiting		Yes	2
14	DIA	311694	On Hold	PRIV	Yes				591	SAPMF05L	300	1982
15	DIA	680358	Running		Yes	1				SAPLZSD_RFC_CUST	300	CDI	Sequential Read	VBAK
16	DIA	250170	On Hold	PRIV	Yes				7	SAPMV45A	300	3054
17	DIA	659714	Waiting		Yes
18	DIA	856380	Running		Yes					SAPLCNPB_W	300	KUPEKAR	Direct Read	PRPS
19	DIA	929894	Running		Yes	8			129	ZFI_CONTRACT_TRACKER2	300	5393
21	DIA	844172	On Hold	PRIV	Yes				483	SAPLSMTR_NAVIGATION	300	648
23	DIA	455014	Running		Yes				128	CL_SALV_BS_TT_MHTML===========CP	300	1068
25	DIA	237984	Running		Yes	1			19	SAPLFAGL_ITEMS_SELECT	300	2213	Sequential Read	BSIS
26	DIA	315758	Running		Yes	1			174	SAPLCNACL	300	464	Sequential Read	PSACL_TAB
28	DIA	758094	On Hold	PRIV	Yes	1			51	SAPMF05L	300	5130
29	DIA	573642	Running		Yes					SAPLTHFB	300	BASIS
38	DIA	307638	Running		Yes	1			19	/1BCDWB/SAPLSF00000075	300	3730	Sequential Read	ESLH
40	DIA	524580	On Hold	PRIV	Yes				545	RM_MEPO_GUI	300	5557
41	DIA	602446	On Hold	PRIV	Yes				466	RM_MEPO_GUI	300	5665

Regards,

NK

[former_member188883]

Hi Nitin,

How much RAM is configured in your application server above ?

Regards,

Deepak Kori

[Former Member]

Online memory is 22400 MB

[Sriram2009]

Hi Nithin

Kindly refer the SAP link about the PRIV mode

Work Process (SAP Library - SAP Memory Management (BC-CST-MM))

Private Memory (SAP Library - SAP Memory Management (BC-CST-MM))

Regards

Sriram

[Former Member]

Hi,

Give us the parameters of the instance profile.

Regards.

Karthik.R

[Former Member]

There are lot of parameters in instance profile. Please let me know which parameter value is meaningful for you and I will paste the details for the same here.

Regards,

NK

[Former Member]

Hi,

Parameters related to memory and wp is needed.

If possible paste the dev_w* logs also.

Regards,

Karthik.R

[former_member188883]

Hi Nitin,

For 22GB RAM you have configured 42 work processes. This could be one of the reasons system is running short of memory.

In SM04 -> Goto --> Memory

check what is the current consumption of each work process.

You may reduce the work process to 25 and check the results.

Also you may control the number of work processes which enter PRIV mode using the parameters

rdisp/wppriv_max_no and

rdisp/max_priv_time

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Thanks Deepak. On what basis you calculated that 42 work processes count is high for 22 GB RAM as I was informed that 1GB RAM can support upto 4 work processes. Do we have standard calculation per GB RAM?

Regards,

NK

[former_member188883]

Hi Nitin,

 I was informed that 1GB RAM can support upto 4 work processes. Do we have standard calculation per GB RAM?

Ideal case 1GB RAM can support 4 work processes . Even in your system you have 42 work processes configured on 22GB RAM. Its not the problem with how many processes are supported with x-number of RAM. But whether your system has enough free memory to process the request.

Each work process in the system will occupy and block certain amount of RAM when SAP starts.

This will reduce the Memory requirement for any other work process.

My suggestion is to reduce the number of work process to release some memory to the system for processing.

Second action would be to analyse which are the tables being access due to which WP is going to PRIV. Ideally when a table is buffered , have complex queries running on them will lead the WP enter PRIV mode as it needs to allocate memory from the buffer.

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Makes perfect sense. I did quick check on the total RAM consumed in SM04 for that app server. SM04 shows consumption of 5500 MB out of total 22400 MB RAM allocated of that lpar. Any inputs?

Secondly, there is no particular table being troublesome, it is the problem with all tables/program overall. However, there are 7 long running jobs since 2 days on that app servers and I feel they are occupying a lot of system resources/memory and hence causing rest DIA work processes to cry for memory and going in PRIV mode. Please correct me if my understanding is wrong?

Regards,

NK

[former_member188883]

Hi Nitin,

However, there are 7 long running jobs since 2 days on that app servers and I feel they are occupying a lot of system resources/memory and hence causing rest DIA work processes to cry for memory and going in PRIV mode. Please correct me if my understanding is wrong?

Above is one of the reasons for WPs going into PRIV mode.

You may check with respective job owners whether these jobs can be deleted. Post that check system behaviour.

Regards,

Deepak Kori

[Former Member]

abap/use_paging                             0

ztta/roll_first                             1024

ztta/roll_area                              6500352

rdisp/ROLL_SHM                              31488

rdisp/ROLL_MAXFS                            250000

rdisp/PG_SHM                                32768

rdisp/PG_MAXFS                              250112

abap/heap_area_dia                          3001024512

abap/heap_area_nondia                       4000317440

abap/heap_area_total                        4000317440

abap/heaplimit                              40894464

abap/swap_reserve                           20971520

ztta/roll_extension                         4000683008

em/initial_size_MB                          8192

em/blocksize_KB                             4096

em/stat_log_size_MB                         20

em/stat_log_timeout                         0

Regards,

NK

[Former Member]

Struggling to get the approval to kill those jobs since morning.

Thanks!!

Regards,

NK

[Former Member]

Hi,

Run the sappfpar check pf=<profile> and the paste the output here.

regards,

Karthik.R

[Former Member]

There are no errors when running sappfpar check pf=<profile>

Regards,

NK

[Former Member]

Just for your information

After cancelling those jobs everything was normal and DIA work processes started working normal without going in PRIV mode as memory resources were released by cancelling those jobs.

Regards,

NK