Several Disp work process runing and consuming Memory

[Former Member]

Hi Folks,

We see some sluggish response from the SAP production system.Looking at the server, there is a high rate of paging going on with several of the disp+work.exe instances with sapservice<sid> user. I did not find any background jobs in active state and also there are enough free work processes. Checked in DPMON aswell.

We have recently updated all support patches in system. also i see some problem with SAPOSCOLL. At os level service seems to be running but when i check in os06 transaction status shows as "not running - process ID not found". Please suggest.

is it normal behaviour that i found total 14 disp work.exe are runing by sapservice<SID> and occupied around 3.7 GB of memory. we have total 6 -dia,2 -Upd,3-bacground,2-spo processes configured. But when i logged in other servers. I didn't find any disp work.exe 's runing in task manager.

Thanks & Regards,

Vinod

[Former Member]

After Rebooting the server the memory does get free but after a certain time it again run's many disp+work processes on OS level.
Rebooting the system always isn't an option. Please suggest a solution.

Regards

Mihir Janaj

[Former Member]

Hai Vinod,

i am facing the same problem now, you could have solved the problem then kindly share the solution with me.

with regards

Sandep

[Former Member]

Problem resolved after rebooting the server

[Former Member]

It is normal to have many disp+work processes - you get one for each work process configured in the system. At system startup they are allocated RAM based on the settings of various profile parameters, and when they are actively processing something they can grab additional RAM from the extended memory pools or operating system heap if needed. This extra memory is released when the WP finishes processing the transaction.

It's common for the saposcol to misbehave after a kernel update, especially if it wasn't stopped properly before the update was applied. It runs in a separate memory area and doesn't always clean up after itself very well. The cleanest way to fix that is to reboot the server. Since the SAP system is stopped during the kernel update anyway, it's a good time to reboot.

[mauricio_ramrezcuevas]

Hi gentlemen,

I have a similar situation on Win2003 32bits, SQLsvr2005, 8GB RAM.

It appears SAP workprocess are using all the resources of memory. CPU is 5% but memory is an issue.

The tasklist shows 11 GB as use of memory, of them the disp+work.exe processes are using 7.7 GB

The strange is that SM50 show just -active- 1 Dialog WP, the rest of WP are -waiting-.

So, why the WP not running are using a lot of memory and why are not releasing it???

Please help!

agent.exe 1196 0 1,012 K

alg.exe 2864 0 2,964 K

cmd.exe 740 0 1,648 K

cmd.exe 7264 0 1,644 K

cpqnimgt.exe 1976 0 5,208 K

CpqRcmc.exe 1260 0 1,368 K

cpqteam.exe 5152 0 2,128 K

cqmghost.exe 2332 0 7,096 K

cqmgserv.exe 2044 0 2,940 K

cqmgstor.exe 2080 0 4,540 K

csrss.exe 464 0 5,080 K

csrss.exe 7552 1 2,596 K

csrss.exe 7100 Console 4 2,644 K

ctfmon.exe 7912 1 360 K

disp+work.exe 5440 0 37,592 K

disp+work.exe 5760 0 652,368 K

disp+work.exe 5768 0 562,548 K

disp+work.exe 5776 0 386,012 K

disp+work.exe 5784 0 332,492 K

disp+work.exe 5792 0 179,600 K

disp+work.exe 5800 0 81,772 K

disp+work.exe 5808 0 35,448 K

disp+work.exe 5816 0 34,544 K

disp+work.exe 5824 0 32,560 K

disp+work.exe 5832 0 47,148 K

disp+work.exe 5840 0 54,528 K

disp+work.exe 5848 0 32,680 K

disp+work.exe 5856 0 34,320 K

disp+work.exe 5864 0 32,636 K

disp+work.exe 5872 0 32,676 K

disp+work.exe 5884 0 32,164 K

disp+work.exe 5892 0 32,672 K

disp+work.exe 5904 0 35,868 K

disp+work.exe 5916 0 32,644 K

disp+work.exe 5932 0 58,372 K

disp+work.exe 5940 0 32,600 K

disp+work.exe 5948 0 32,232 K

disp+work.exe 5956 0 33,584 K

disp+work.exe 5968 0 32,712 K

disp+work.exe 5976 0 32,284 K

disp+work.exe 5984 0 32,260 K

disp+work.exe 5992 0 538,904 K

disp+work.exe 6000 0 262,756 K

disp+work.exe 6008 0 107,744 K

disp+work.exe 6016 0 31,900 K

disp+work.exe 6024 0 32,224 K

disp+work.exe 6032 0 89,308 K

disp+work.exe 6044 0 31,880 K

disp+work.exe 6056 0 31,984 K

disp+work.exe 6064 0 31,876 K

disp+work.exe 6072 0 31,640 K

disp+work.exe 6080 0 387,476 K

disp+work.exe 6088 0 283,932 K

disp+work.exe 6096 0 286,920 K

disp+work.exe 6104 0 220,844 K

disp+work.exe 6112 0 143,888 K

disp+work.exe 6132 0 111,424 K

disp+work.exe 2400 0 138,852 K

disp+work.exe 540 0 191,112 K

disp+work.exe 2796 0 104,972 K

disp+work.exe 1856 0 208,540 K

disp+work.exe 424 0 82,228 K

disp+work.exe 4468 0 45,172 K

disp+work.exe 2412 0 31,468 K

disp+work.exe 6232 0 31,460 K

disp+work.exe 6240 0 31,932 K

disp+work.exe 6248 0 31,924 K

disp+work.exe 7384 0 613,432 K

disp+work.exe 2764 0 653,032 K

explorer.exe 5080 0 14,832 K

explorer.exe 7928 1 10,480 K

gwrd.exe 5728 0 51,100 K

hpsmhd.exe 2264 0 11,232 K

hpsmhd.exe 2716 0 17,272 K

icman.exe 5736 0 9,800 K

igsmux.exe 5472 0 13,504 K

igspw.exe 5568 0 24,988 K

igspw.exe 5576 0 24,988 K

igswd.exe 5448 0 2,412 K

jusched.exe 5160 0 2,044 K

locator.exe 1788 0 2,336 K

logon.scr 8156 Console 4 1,528 K

lsass.exe 548 0 12,144 K

ManagementConsole.exe 7884 0 21,992 K

mmc.exe 7256 1 2,220 K

mmc.exe 4256 0 11,012 K

mmc.exe 6920 0 21,848 K

mms.exe 2244 0 50,904 K

msdtc.exe 1076 0 4,484 K

msftesql.exe 1400 0 4,544 K

msg_server.exe 5432 0 7,688 K

rdpclip.exe 2964 0 3,300 K

RemComSvc.exe 7664 0 1,352 K

rotatelogs.exe 2540 0 1,932 K

rotatelogs.exe 2548 0 1,908 K

rotatelogs.exe 2992 0 1,940 K

rotatelogs.exe 3000 0 1,916 K

saposcol.exe 1816 0 15,348 K

sapstartsrv.exe 1868 0 21,284 K

schedhlp.exe 5168 0 2,788 K

schedul2.exe 1212 0 4,008 K

services.exe 536 0 46,180 K

smhstart.exe 1908 0 3,308 K

smss.exe 416 0 464 K

snmp.exe 1896 0 5,816 K

spoolsv.exe 1052 0 5,796 K

SQLAGENT90.EXE 2724 0 4,416 K

sqlservr.exe 1456 0 1,685,356 K

SqlWb.exe 764 0 64,440 K

svchost.exe 724 0 3,048 K

svchost.exe 792 0 4,076 K

svchost.exe 856 0 4,576 K

svchost.exe 892 0 3,700 K

svchost.exe 908 0 22,764 K

svchost.exe 1340 0 2,248 K

svchost.exe 1700 0 10,552 K

svchost.exe 2800 0 4,940 K

svchost.exe 468 0 4,088 K

sysdown.exe 2312 0 1,608 K

System 4 0 252 K

System Idle Process 0 0 28 K

tasklist.exe 6592 0 3,904 K

taskmgr.exe 7228 0 2,056 K

TimounterMonitor.exe 5192 0 6,052 K

TrayMonitor.exe 5200 0 5,948 K

vcagent.exe 1284 0 7,128 K

winlogon.exe 488 0 4,916 K

winlogon.exe 7592 1 2,040 K

winlogon.exe 5332 Console 4 4,768 K

wmiprvse.exe 2200 0 5,340 K

wmiprvse.exe 2616 0 12,196 K

[Former Member]

Hi Mauricio:

Did you fix the problem?

We are experiencing the same problem on W2003+DB2.

Thanks in advance.

[Former Member]

Hi,

Restart the SAP OS collector as root at OS level, from /usr/sap/SID/exe or sapmnt/SID/exe

1. saposcol -k

2. saposcol -f

3. saproot.sh SID

4. saposcol -l

Now see if it helps, this way you will clear the exisitng collector and reset the permisions and start it.

Hope this helps,

Sanjay

[JPReyes]

Check the collector logs for details... did you give the saposcol the addecuate rights when you changed the kernel?...

But when i logged in other servers. I didn't find any disp work.exe 's runing in task manager.

Click on "show processes from all users" in the Task Manager

Regards

Juan

[Former Member]

Hi Juan,

Thanks for your prompt response.

I see message as " OSCOLL not running (process ID not found). . I did not change any permissions during kernel upgrade.I see saposcol service is running with user "<SID>ADM user. Below is log message.

As i said earlier i checked in processes tab in task manager but i did not find like 14 disp+work.exe processes are running with SAPservice <SID> user. Please suggest.

OSCOLL Log:

HWO description

SAPOSCOL version COLL 20.90 700 - 20.54 NT 06/06/06, 64 bit, multithreaded, Non-Unicode

compiled at Oct 12 2006

systemid 562 (PC with Windows NT)

relno 7000

patch text COLL 20.90 700 - 20.54 NT 06/06/06

patchno 80

intno 20050900

running on NEWLOTS Windows NT 5.2 3790 Service Pack 2 4x AMD64 Level 6 (Mod 15 Step 6)

23:13:07 22.02.2010 LOG: Profile : no profile used

23:13:07 22.02.2010 LOG: Saposcol Version : [COLL 20.90 700 - 20.54 NT 06/06/06]

23:13:07 22.02.2010 LOG: Working directory : E:\usr\sap\PRFCLOG

23:13:07 22.02.2010 LOG: Allocate Counter Buffer [10000 Bytes]

23:13:07 22.02.2010 LOG: Allocate Instance Buffer [10000 Bytes]

23:13:07 22.02.2010 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0

23:13:07 22.02.2010 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0

23:13:07 22.02.2010 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0

23:13:07 22.02.2010 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0

23:13:07 22.02.2010 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0

23:13:07 22.02.2010 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0

23:13:07 22.02.2010 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0

23:13:07 22.02.2010 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0

23:13:07 22.02.2010 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0

23:13:07 22.02.2010 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0 23:13:08 22.02.2010 LOG: Shared Memory Size: 77198.

23:13:08 22.02.2010 LOG: Shared Memory was created by process:13288

23:13:11 22.02.2010 LOG: Collector daemon started

23:13:11 22.02.2010 LOG: read coll.put Mon Feb 22 23:01:24 2010

23:13:11 22.02.2010 LOG: Collector PID: 13288

23:13:21 22.02.2010 LOG: Process Monitoring active.

23:13:21 22.02.2010 LOG: searching for Process Monitoring Templates in E:\usr\sap\PRFCLOG\dev_proc

23:13:21 22.02.2010 LOG: searching for Process Monitoring Templates in E:\usr\sap\PRFCLOG\procmon\

23:13:21 22.02.2010 LOG: The following processes will be monitored:

Collector Versions

running COLL 20.90 700 - 20.54 NT 06/06/06

dialog COLL 20.95 700 - 20.68 NT 09/03/27

Shared Memory attached

Number of records 725

Active Flag active (01)

Operating System Windows NT 5.2.3790 SP 2 4x AMD64 Level 6

Collector PID 13288 (000033E8)

OpenProcess failed, lasterror 5

Collector not running (process ID not found).

Start time coll. Mon Feb 22 23:13:11 2010

Current Time Tue Feb 23 14:59:51 2010

Last write access Tue Feb 23 14:59:42 2010

Last Read Access Tue Feb 23 14:58:46 2010

Collection Interval 10 sec (next delay).

Collection Interval 10 sec (last ).

Status free

Collect Details required

Refresh required

Header Extention Structure

Number of x-header Records 1

Number of Communication Records 60

Number of free Com. Records 60

Resulting offset to 1.data rec. 61

Trace level 2

Collector in IDLE - mode ? NO

become idle after 300 sec without read access.

Length of Idle Interval 60 sec

Length of norm.Interval 10 sec

Thanks in advance for any suggessions.

Regards,

Vinod

[JPReyes]

try to kill and restart the saposcol manually... then post the errors..

stop

saposcol -k

start

saposcol -l

Regards

Juan