Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Work Processes stuck at action Commit

Hi All

Our 4.6C system has developed a strange performance problem.

We are finding situations where multiple work processes are all in status Commit, and remain so until the either time out or cancelled. They are performing quite different workloads, don't appear to be waiting for any locks, and don't actually appear to be committing from an AS/400 view. Has any one else encountered this. I've attached an SM50. We are also opening in OSS call. But I thought I'd tap the real knowledge as well.

No Ty. PID Status Reasn Start Err Sem CPU Time Report Cl. User Action Table

2 DIA 11886 Running Yes 1 SAPMV45A 410 GALLACL Sequential read VBAK

22 DIA 11907 Running Yes 65 ZSDRP022 410 PERCHAM Sequential read VBPA

23 DIA 11908 Running Yes 2 SAPLM61X 410 OBRIENC Sequential read MSSQ

6 BGD 11890 Running Yes 20600 ZMMRP007 410 BATCH Direct read SER03

1 DIA 11885 Running Yes 2298 SAPLOLEA 410 NAIRNPA Commit

3 BGD 11887 Running Yes 9737 SDRQCR21 410 BATCH Commit

7 BGD 11891 Running Yes 886 SAPLZCGF 410 CHECKER1 Commit

14 DIA 11899 Running Yes 1690 SAPMM07M 410 KILDEAV Commit

15 DIA 11900 Running Yes 1400 SAPLOLEA 410 BULLIOR Commit

19 DIA 11904 Running Yes 543 SAPLOLEA 410 STEVENA Commit

25 UPD 11910 Running Yes 1 RSM13000 410 MACINTK Commit

31 BGD 11917 Running Yes 834 SAPLZCGF 410 CHECKER1 Commit

32 BGD 11918 Running Yes 14505 SAPLZCGF 410 CHECKER1 Commit

0 DIA 11884 waiting Yes

4 BGD 11888 waiting Yes

5 BGD 11889 waiting Yes

8 BGD 11893 stopped CPIC Yes 3 SAPLRSAP 410 BW_REMOTE

9 DIA 11894 waiting Yes

10 DIA 11895 Running Yes 410 CAMPBEC

11 DIA 12218 Running Yes SAPLTHFB 410 JONESST

12 DIA 11897 Running Yes 3 SAPLRSAP 410 BW_REMOTE

13 DIA 11898 waiting Yes

16 DIA 12219 waiting Yes 1

17 DIA 11902 waiting Yes

18 DIA 11903 waiting Yes

20 DIA 11905 waiting Yes

21 DIA 11906 waiting Yes

24 UPD 11909 waiting Yes

26 ENQ 11911 waiting Yes

27 DIA 11912 waiting Yes

28 DIA 11914 waiting Yes

29 DIA 11915 waiting Yes

30 BGD 12230 waiting Yes 1

33 SPO 11919 waiting Yes

34 UP2 11920 Running Yes SAPLIEP2 410 CAMPBEC

Regards

Steve

Former Member
replied

This looks like a problem with the database monitor (QQQDBLOG and QQQDBMWL in the call stack). You may want to report this problem to IBM (including the call stack information that you sent me). As a workaround, you can disable the monitor by setting profile parameter as4/dbmon/enable = 0. However, you won't see any useful data in ST04 then.

Kind regards,

Christian Bartels.

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question