SAPOSCOl is not starting due to shared memory not attached

[former_member262203]

Dear gurus,....
My env is AIX.enough page file is allocated and usage is only 3%.but unable to start saposcol
Plz guide

[sashibhushan_sahu2 · Accepted solution]

Hi,

Please kill the SAPOSCOL process and clean the shared memory.

Find "4dbe4" and kill it .

to remove use the below command

ipcrm -m "XXXX"  .

where XXXX is the shared memory key for 4dbe4 .

Regards

sashi

[Former Member · Accepted solution]

Hi Sharad,

Please go through below mentioned sap notes..

548699 - FAQ: OS collector SAPOSCOL

165188 - saposcol not running on AIX-DB2

You can also try these steps..

Execute command:

u201Cipcs -mau201D and note the line that contains saposcol key u201C4dbeu201D.

You need the shared memory ID.

After that, execute command: ipcrm -m ID

Now the command: u201Csaposcol -su201D should show that saposcol is not running and that the shared memory is not attached. The shared memory key will be created automatically by the saposcol when the collector is next started with the command: u201Csaposcol -lu201D.

----OR----

Clearing SAPOSCOL Shared Memory Segment:

Use the following procedure to delete the shared memory for SAPOSCOL:

saposcol -d            (start in dialog mode)

Collector > clean

Collector > quit

saposcol -k            (stops saposcol)

saposcol -d            (before restarting)

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

Collector > quit

cd /usr/sap/tmp

mv coll.put coll.old (rename the file; this stores the saposcol history data)

cd

saposcol                (start saposcol again)

If you cannot delete the shared memory segment with the above procedure then:

On UNIX systems:

You can use 'cleanipc 99 remove' on O/S level (this will remove all the ipc objects for the system number 99, also for the SAPCCMSR agent)

You could alternatively use 'ipcrm -M 0x00004dbe', which will delete saposcol’s SHM, but not anything related to host agent

On UNIX systems you can use the SAP OS command ‘showipc 99’ to report the defined IPC objects for the system area 99.

You can also use the UNIX command ‘ipcs –a’ to report some more detailed information, like owner and permissions about the defined IPC objects.

Regards,

Prithviraj.

[former_member262203 · Accepted solution]

HI Shashi ...Thanks for your respone
firstly it was showing (with root user only)..but showing nothing

My env is AIX+Sybase ASE
hi prithvi and sriram...

i have tried saposcol command and also have used ST06 but not succeed.

[former_member262203]

Thanks all...it worked...as u siad ....i followed  Former Member...
at last not least thanks ...

[alwina_enns]

Dear Sharad,

is saposcol started by the SAPHOSTAGENT? If yes, please do not stop the saposcol with "-k" and do not start it with "-l", these parameters are obsolete, the whole SAPHOSTAGENT should be stopped and started. Please take a look at the SAP note "2180367 - How to run saposcol OS collector correctly".

In case saposcol is a part of the SAPHOSTAGENT take a look at the SAP note "2179983 - Basic 'missing OS data' troubleshooting" how to cleanup the shared memory of saposcol.

Regards, Alwina

[sashibhushan_sahu2]

Dear Sharad,

It should work if you follow Prithvi's given Note.

Pl try once again....

Do the following steps :

1. saposcol -d   stop saposcol

2. saposcol -s   check the status

3. ps -ef|grep sapsoscol  -------if it exist then kill the process id kill -9 "XXXX"

4. search for shared memory key for 4dbe , if it exist then ipcrm -m "XXXXX"

5. Also check permission of saposcol  ( ls - l saposcol

chown root saposcol

chgrp sapsys saposcol

chmod 4750 saposcol

If it doesnt start then you have to reboot the OS .

[Sriram2009]

Hi Sharad

You can Stop & Start the SAPOSCOl manually from transaction code ST06N/ST06/OS07N during off peak time.

Regards

SS

[former_member262203]

Thanks i have olready tried..it