Basis Ticket :

We have the ECC 5.0 installed on the HP UX. Whenever I am trying to run the t-co
de ST06 for the application server of the production, I am getting one message "
SAPOSCOL is busy, try again". I am able to get the run the ST06 for other applic
ation servers.
The current version what we have for Saposcol is : Version: COLL 20.87 640 - hpx
Oscol 07/2003.
It will be a great favour if anybody can provide me the steps from the scrach in
how to run the SAPOSCOL.
1) login as <sid>adm
2) check if your saposcol is running at unix level
ps -ef | grep saposcol
3) go to /sapmnt/NPD/exe
Check if saposcol file is existing
Check the owner and the permission of the file
To start SAPOSCOL with the command saposcol (or saposcol -l).
Saposcol can run independent of the SAP system, so you can try to start it indiv
idually using:
Try to start saposcol with command saposcol -l
You can know status of the saposcol by saposcol -s and stop it by saposcol -k
---
Try to check, if you have cleaned up Share memory present in /usr/sap/tmp/dev_co
ll & try to get latest patch of SAPOSCOL.
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 comm
ands 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