cancel
Showing results for 
Search instead for 
Did you mean: 

No dialog process free

Former Member
0 Kudos

HI Experts,

I am facing a unique issue here

No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User Action Table

-


0 DIA 19557 Run no 0 4 0

1 DIA 19558 Run no 0 4 0

2 DIA 19559 Run no 0 4 0

3 DIA 19560 Run no 0 4 0

4 DIA 19561 Run no 0 4 0

5 DIA 19562 Run no 0 4 0

6 DIA 19563 Run no 0 4 0

7 DIA 19564 Run no 0 0 0

8 DIA 19565 Run no 0 4 0

9 DIA 19566 Run no 0 4 0

10 UPD 19567 Run no 0 4 0

11 ENQ 19568 Run no 0 4 0

12 BTC 19569 Run no 0 4 0

13 BTC 19570 Run no 0 4 0

14 BTC 19571 Run no 0 4 0

15 SPO 19572 Run no 0 4 0

16 UP2 19573 Run no 0 4 0

All process are occupied none are.

Sappfpar showed error in check, corrected it still same issue

***ERROR: Size of shared memory pool 40 too small

================================================================

SOLUTIONS: (1) Locate shared memory segments outside of pool 40

with parameters like: ipc/shm_psize_<key> =0

SOLUTION: Increase size of shared memory pool 40

with parameter: ipc/shm_psize_40 =208000000

Kindly suggest

Edited by: Ameya Joshi on Jan 18, 2010 11:58 PM

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Kill some of Dialog work processes from OS level by using dpmon

And increase your Dialog processes based on your business requirement....seems you are running your system with very less dialog processes compare to your user accounts/requirement.

Regards,

Nick Loy

Former Member
0 Kudos

Hi Amber,NIck,Anil

I think you people didnt see the the process table properly

No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User Action Table

0 DIA 19557 Run no 0 4 0

1 DIA 19558 Run no 0 4 0

2 DIA 19559 Run no 0 4 0

3 DIA 19560 Run no 0 4 0

4 DIA 19561 Run no 0 4 0

All the dialog process are in run state but as you can see not a single transaction is being executed. This was quite surprising for a newbie like me.

Not a single program/job is running still all processes are in run state.

My question has anybody encountered such issue?

What is reason behind this behaviour of processes?

SAP SCM version 5.00

DB is Maxdb 7.6

OS is linux

Kindly if possible answer my queries

Former Member
0 Kudos

Make sure database is up and running.

Then check log files of your work processes (dev_w*) for more information.

JPReyes
Active Contributor
0 Kudos

The first thing you need to know is what is triggering the processes.... so please post the contents of dev_w0

Regards

Juan

Former Member
0 Kudos

Hi Juan,

Well the trace files didnt provide any valuable hint ....but i will post it for you

dev_w0 contents

db connect

+M Mon Jan 18 23:51:51 2010+

+M kernel runs with dp version 241000(ext=110000) (@(#) DPLIB-INT-VERSION-241000-UC)+

+M length of sys_adm_ext is 576 bytes+

+M ***LOG Q01=> ThInit, WPStart (Workproc 0 1 6160) [thxxhead.c 1290]+

+M ThInit: running on host ecddbci+

+M calling db_connect ...+

+C+

+C INFO : SAP DB Packet_Size = 131072+

+C INFO : SAP DB Min_Reply_Size = 4096+

+C INFO : SAP DB Comm_Size = 126976+

+C INFO : DBSL buffer size = 126976+

+C INFO : SAP DB MaxLocks = 800000+

+C INFO : Connect to DB as 'SAPECD'+

+C Command info enabled+

+C Now I'm connected to SAP DB+

+C 00: nlxsit03-ECD, since=20100118235151, ABAP= <unknown> (0)+

+B Connection 0 opened (DBSL handle 0)+

+B Wp Hdl ConName ConId ConState TX PRM RCT TIM MAX OPT Date Time DBHost+

+B 000 000 R/3 000000000 ACTIVE NO YES NO 000 255 255 20100118 235151 nlxsit03+

+C INFO : SAP RELEASE (DB) = 701+

+M db_connect o.k.+

+M vmcj/sgc_options: switch off delayed session cleanup during shared gc+

+M vmcj/sgc_options: switch off template cleanup before cloning+

+J extMemCheck is set to dw.sapECD_DVEBMGS00.0x6209f0+

+J extGcMemReserve is set to dw.sapECD_DVEBMGS00.0x621520+

+J extGcMemCommit is set to dw.sapECD_DVEBMGS00.0x621490+

+J extGcMemFree is set to dw.sapECD_DVEBMGS00.0x6213f0+

+J extCreateSharedCodeCache is set to dw.sapECD_DVEBMGS00.0x625420+

+J extSetSharedCodeCachePerm is set to dw.sapECD_DVEBMGS00.0x624480+

+J extMalloc is set to dw.sapECD_DVEBMGS00.0x624020+

+J extCalloc is set to dw.sapECD_DVEBMGS00.0x623ee0+

+J extRealloc is set to dw.sapECD_DVEBMGS00.0x624340+

+J extFree is set to dw.sapECD_DVEBMGS00.0x624250+

dev_disp trace file

+kernel runs with dp version 241000(ext=110000) (@(#) DPLIB-INT-VERSION-241000-UC)+

+length of sys_adm_ext is 576 bytes+

+*** SWITCH TRC-HIDE on ***+

+***LOG Q00=> DpSapEnvInit, DPStart (00 6151) [dpxxdisp.c 1286]+

+shared lib "dw_xml.so" version 39 successfully loaded+

+shared lib "dw_xtc.so" version 39 successfully loaded+

+shared lib "dw_stl.so" version 39 successfully loaded+

+shared lib "dw_gui.so" version 39 successfully loaded+

+shared lib "dw_mdm.so" version 39 successfully loaded+

+rdisp/softcancel_sequence : -> 0,5,-1+

+use internal message server connection to port 3900+

+MtxInit: 30000 0 0+

+DpSysAdmExtInit: ABAP is active+

+DpSysAdmExtInit: VMC (JAVA VM in WP) is active+

+DpIPCInit2: start server >ecddbci_ECD_00 <+

+DpShMCreate: sizeof(wp_adm) 29784 (1752)+

+DpShMCreate: sizeof(tm_adm) 6009216 (29896)+

Regards,

Ameya

Edited by: Ameya Joshi on Jan 22, 2010 6:59 AM

Former Member
0 Kudos

Hello Joshi,

The problem seems to be with the shared memory.

Please clear shared memory and start all the services and start SAP again.

Clearly no transaction was running,it is only pure resource problem.

Thanks,

Best Regards,

Shaym Dontamsetty

former_member198270
Active Contributor
0 Kudos

Hello Ameya, As the log says all the dialog processes are consumed. You might not be able to login at SAP.

can you please cancel some dialog process(old and invalid) and once deleted you can access thru SAP level and find out what might be the root cause of the issue. Like some parallel jobs are getting triggerred simultaneously and consuming all WP's.

Hope it helps.

PS : if you could provide your SAP, OS and DB details it will be very helpful. Thanks

Regards, Amber S

former_member227283
Active Contributor
0 Kudos

Hi,

If all the dialog process are full then you dont have any option to do.

Rather than wait for the activity which has occupied the dailog process to complete or kill the process if it is not in use.

Thanks

Anil