ST06 SAPOSCOL not running?(shared memory not avilable)

[Former Member]

Dear All :

when I checked the system information via SAP GUI with ST06/OS06/OS07,

I found that the saposcol's status "not running (shared memory not avialable).

and I checked saposcol running on our server. -but "status -s" returns

incorrectly, status: not running (process ID not found).

Pls tell me how I can figure this?

Status now

**************************************************************

Collector Versions :

running : COLL 20.94 700 - 20.58 NT 07/04/27

dialog : COLL 20.95 700 - 20.65 NT 08/02/06

Shared Memory : attached

Number of records : 575

Active Flag : active (01)

Operating System : Windows NT 5.2.3790 SP 2 SAPPRD01 4x IA64 Level 32

Collector PID : 0 (00000000)

Collector : not running (process ID not found).

Start time coll. : Fri Aug 07 22:02:00 2009

Current Time : Thu Oct 29 10:30:52 2009

Last write access : Wed Oct 14 12:11:34 2009

Last Read Access : Wed Oct 28 19:35:09 2009

Collection Interval : 10 sec (next delay).

Collection Interval : 10 sec (last ).

Status : read

Collect Details : required

Refresh : required

Header Extention Structure

Number of x-header Records : 1

Number of Communication Records : 60

Number of free Com. Records : 61

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

[anindya_bose · Accepted solution]

go to command prompt

run "saposcol -d" ..it will open SAPOSCOL in dialog mode. You will get a prompt from Collector

then run , "kill" and then "leave"

Come back to windows command prompt again and restart saposcol by running command "saposcol -l"

1. "......sidadm>saposcol -d"

2. "Collector>kill"

3. "Collector >leave"

4. "......sidadm>saposcol -l"

[Former Member · Accepted solution]

My question haven't been sloved according to your answered

[anindya_bose · Accepted solution]

Hi

Check in windows services ( From run , type services.msc and press enter) with which account SAPOSCOL is running.

Probably in your case SAPSERVICE<SID>. Change the user to <SID>ADM, maintain the password for SIDADM.

Stop SAP, Stop Database, Restart Window server. Then Start Database, Start SAP and check if SAPOSCOL service is running.

[Former Member · Accepted solution]

Dear Anindya:

Thanks very much, my problem has been solved after restaring the server.

Thanks

BR

ShuMin Wan

[Former Member]

Hi,

Kernel upgrade is not the solution for this situation, cause this is a well known and common situation.

your system is not able to allocate shared memory to SAPOSCOL service, just restart your machine(this is best solution to free up shared memory on windows platform).

As well as check whether SAPOSCOL service status, and try to restart....before going to perform above activity.

Regards

Nick Loy

[Former Member]

Dear Nick:

Really thanks for your answer, my problem has been solved arrcording to your advise.

Thanks

Best Regards,

ShuMin

[Former Member]

After checking all necessary parameters i.e. SAPCOL Services, permission, restarting the machine, restarting the sap instance the problem not resolve.

SAPOSCOL service stop automatically.

Collector Versions

running COLL 20.94 700 - 20.58 NT 07/04/27

dialog COLL 20.94 700 - 20.58 NT 07/04/27

Shared Memory attached

Number of records 473

Active Flag active (01)

Operating System Windows NT 5.2.3790 SP 2 hostname13 2x Intel 80686

Collector PID 1608 (00000648)

AdjustTokenPrivileges failed with 1300

OpenProcess failed, lasterror 5

Collector not running (process ID not found).

Start time coll. Tue Dec 29 03:03:39 2009

Current Time Tue Jan 05 22:51:56 2010

Last write access Tue Jan 05 22:51:54 2010

Last Read Access Tue Jan 05 22:36:50 2010

Collection Interval 60 sec (next delay).

Collection Interval 70 sec (last ).

Status read

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 ? YES

become idle after 300 sec without read access.

Length of Idle Interval 60 sec

Length of norm.Interval 10 sec

Any work around.

~ Prasanta

[Former Member]

Do this :

Check if you are able to stop SAPOSCOL :

SAPOSCOL -d ( into interactive mode)

Then

STOP

You might get an error saying that process still exists ; but u cant kill the process..

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

If you are getting a shared memory error then do ;

ipcs -ma | grep '4dbe' --> It will show similar to Process ID and running with root ;

u have to kill the shared memory segment

ipcrm -ma <process ID> ( This needs to be done with root )

Let me know the update please

I have faced the issue several times ; and it has been resolved by above action.

SAPnote to use : 548699

Thanks

Rishi

[Former Member]

Dear Rishi:

But how to do in windows?not unix.

Thanks

BR

[Former Member]

Thanks Dude..

It worked.

Edited by: sankar.bheema on Apr 19, 2011 1:25 PM

[Former Member]

Hi,

Mostly you need to go for kernel upgrade as mentioned in SAP notes 522453 & 1013331.

Check this thread for more details.

Thanks,

Sushil

[Former Member]

Dear Sushil:

You advised to updated the Kernel, But what will be effected after updated?

Thanks

Best Regards,

ShuMin Wan