OS06 -> NO values found

[Former Member]

Hi all,

I have problem with my saposcol ( ECC6 (as ABAP) IBM-AIX,Oracle) . SAPOSCOL is running fine, But not able to stop.

from SAP i am trying to stop and restart. IN SAP OS06-> status it is showing running, if i try to stop it will not respond, it will take you main OS06 screen.

Same problem with OS level saposcol -k ---> will not able to kill process. if i try to kill manually kill -9 PID it say PID not exit.

saposcol -s showing all values. (with PID and running status).

• I have 3 different instance in same host.

saposcol have root:sapsys rights.

• there is no any shared memory problem.

please let me know how to trouble shoot and resolve this problem

Regards,

satish.

[Former Member]

HI Guy's

i checked lot of sap notes..all notes are refer only...standard procedure....but standard procedure will not work here...i got solution from my UNIX team.

please follow the below procedure....it works

solution is:

6. Question: How do I stop saposcol if standard commands (points 2

and 3) do not work (Unix)?

Answer: Sometimes it may be impossible to stop saposcol either by u201Csaposcol -du201D --> kill or by u201Csaposcol -ku201D. The system produces messages similar to:

can't kill process 34570.

kill: No such process

ERROR:No reaction from collecting process 34570!

Please kill collecting process.

Although no process with PID 34570 exists, the output of command u201Csaposcol -su201D shows that saposcol is running and shared memory is attached. In this case, you can execute command: "cleanipc 99 remove".

If this does not work either, it is possible to stop the collector running by removing the shared memory key of saposcol.

7. Question: How do I remove the shared memory key of saposcol?

Answer: Sometimes it may be necessary to remove the shared memory key of saposcol (see point 6).

Caution: Please be very careful! This procedure should be performed only after checking that saposcol is really not running (see point 4)

and only in cases when other options (see point 6) really do not work!

For this, 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: u201Csaposcol -lu201D

[former_member524429]

Hi,

Please check if your saposcol version is current or not.

A current version of saposcol should be used according to your OS.

If you want to replace saposcol, delete the coll.put file (located at /usr/sap/tmp) and install a new saposcol version as specified in Note 19227.

Regards,

Bhavik G. Shroff