on 06-18-2015 11:41 AM
Hello Folks,
SM50 dia and btc wp are not updated after parameter change. I have changed the parameter taken restart of the servers.
However it is not updated in SM50 also the wp parameters got updated in rz11, total wp number also got updated.
Urgent please help. My system is on EHP7 NW 740 SP08, Kernel release 742 101.
Also I noticed in SM50 work process number range changed say I increased dia wp to 20. I can see dia wp 1-10 in SM50 , and the next sequence starts with 21 for the btc wp (10 - 20 dia wp should be there but for some reason it is not utilized).
Hi Balaji,
I believe Dummy operation mode is not getting updated after restart of the system.
So follow the below steps
- Check the number of dia and btc workprocess in Dummy operation mode
- If it is showing the old value then Delete the dummy operation mode from the system
- Then take a restart of the system.
- On restarting , it may hopefully pick up the new value
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Balaji,
Follow the below steps
- Change the BTC and DIA workprocess to 21 instead of 30.
- Take a restart of SAP system.
If it is getting increase to 21 , then you have to change the parameter of rdisp/wp_max_no.
Also do paste the logs for dev_disp and dev_w0
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you just need to fix the operation modes from RZ04 and RZ03.
Fix the number of processes for each modes.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To to create and force apply in run time.
Also, what is the value of rdisp/wp_max_no ?
Read below to understand more more on this
During the start-up of the server, the work processes resulting from the following parameters are started: rdisp/wp_no_dia, rdisp/wp_no_vb rdisp/wp_no_vb2, rdisp/wp_no_enq, rdisp/wp_no_btc, and rdisp/wp_no_restricted. The total of the parameters must be smaller than or equal to the value of parameter rdisp/wp_max_no.
Regards,
Yes it has been updated properly in RZ11 too I checked already.
You want me to set DEFAULT values to rdisp/configurable_wp_no?
that will set the count similar to rdisp/wp_max_no right?
Also if you had noticed in the beginning of the thread i mentioned "SM50 work process number range changed say, I increased dia wp to 20. I can see dia wp 1-10 in SM50 , and the next sequence starts with 21 for the btc wp (10 - 20 dia wp should be there but for some reason it is not utilized"). Any thot on that?
Hello Balaji,
in which profile you have set the parameters - instance or default profile? Please share the values for all rdisp/wp* parameters as Divyanshu has requested. The work processes are started by the dispatcher, please check its trace dev_disp for any errors or warnings during startup.
Regards,
Alwina
Hello Balaji,
please check the documentation:
for the parameter rdisp/configurable _wp_no:
"Caution This parameter should have default value DEFAULT. Only change the value in exceptional situations and after consulting SAP."
Regards,
Alwina
Hi Alwina,
Thanks for the response.
I did not change the parameter rdisp/configurable _wp_no, value automatically appears as the total number of WP in the system.
As mentioned already here are the values in one of the appln server affected
dia wp - 30 btc wp - 30 spo - 3 , vb - 4 , vb2 - 2
rdisp/configurable_wp_no parameter value - 69 (30+30+3+4+2)
rdisp/wp_max_no - 74 (total wp + 5 )
Am seeing the below info in dev_disp log
Thu Jun 18 04:54:05 2015
***LOG Q1O=> DpWpConf, WP Conf () [dpxxwp.c 2805]
*** WARNING => DpWpConf: sum (standby + dyn) (0+2) < max - conf (26-21) [dpxxwp.c 3075]
***LOG Q1P=> DpWpConf, MaxConfig () [dpxxwp.c 3078]
***LOG Q1Q=> DpWpConf, MaxConfig () [dpxxwp.c 3084]
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.