cancel
Showing results for 
Search instead for 
Did you mean: 

SAPOSCOL not running ? (shared memory not available )

Former Member
0 Kudos

Hi,

When I check t code st06 , I get message saying "SAPOSCOL not running ? (shared memory not available )" , I'm on ECC 5.0 and having kernel release 640 Linux GNU SLES-7 i686 A with patch level 247. Also the SAPOSCOL Collector Version: COLL 20.88 640 - V1.12 for Linux. The same version is running on my Development server, whereas I'm getting this msg in prd. Can anybody suggest ??

Thanks & Best Regards,

Atul K

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

check detail analysis->file system->file system monitor

other option is go to RZ20->SAP CCMS Monitor Templates->Operating System

Then start SAPOSCOL (got to ST06)

wait some moment

if not start then increase the swap (virtual memory) for windows

set system managed size

for AIX

<sid>adm

#saposcol -d

#collector>clean

#collector>quit

#saposcol -k    for stop the collector

before restarting

#saposcol -d

#collector >leave

#collector>quit

#cd/usr/sap/tmp

#mv coll.put coll.put sav

#cd

#saposcol

After restart the system check ST02

click on SWAP-> Table definition -> current parameter

"rsdb/ntab/entrycount"

or go to RZ10

instance profle

default value=20000

increase=30000

http://vishalchaudharybasis.blogspot.in/2014/08/saposcol-not-running-shared-memory-not.html

Former Member
0 Kudos

replaced with the latest saposcol.

Former Member
0 Kudos

Hi Atul

let us know if the problem resolved, however, shared memory cleanup can be done as follows:

1)Login with the user <sid>adm and perform these steps

saposcol -d

Collector > clean

Collector > quit

saposcol -k to stop the collector.

Before restarting

saposcol -d

Collector > leave (You should get a message Shared memory deleted)

Collector > quit

cd /usr/sap/tmp

mv coll.put coll.put.sav

cd

saposcol

"coll.put" ,if this file contains the old shared memory and should be

deleted in order to get a clean start. Please look at the SAP Note

548699 and follow point 7 very carefully:

If you are unsuccessful in clearing shared memory, please try the

following commands to clear the shared memory:

2)

$ saposcol -kc

$ saposcol -f

If this doesn't work, then try:

3)

cleanipc 99 remove on the O/S level (Check note #548699 first)

4) If not you have to do a OS level restart to fix the issue.

Also check if new saposcol can be applied as per Note 19227

Bhudev

Former Member
0 Kudos

Hello Atul,

just go to OS level and as user <sid>adm

stop the SAPOSCOL using saoscol -k

and then start it again using saposcol -d

It should be fine

If the problem reoccurs,think of going for new version of saposcol

Rohit

Former Member
0 Kudos

Hi Atul,

Even after saposcol -k and -l it doesn't start, then try to delete the shared memory and starting the saposcol by going into interactive mode

Bhudev