on 09-08-2011 11:39 AM
Hi All,
Several times we have found that SAPOSCOL was not running on my ECC6.0 Server.
OS - HP UNIX
As per my understanding whenever we down SAP and start it SAPOSCOL automatically get started with startsap script.
So if we find SAPOSCOL down, I expect somebody should intentionaly down it otherwise it should not be down.
Please let me know what could be other reasons of it or do we have anywhere log file available for it.
When we find SAPOSCOL down and we start it, it get start easily.
Please suggest.
Shivam Mittal
Some times it happens with insuf shared memory also, Just check when was it happended and how much time it was out.
I suggest to check the start/stop sequence with users to make sure the sufficient parmissions and the automatic stat with startsap.
Regards,
Nick Loy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
If you suspect that somebody is killed the saposcoll process, manually, you can trace it by looking ".sh_history" in each user home folder at the OS level, to find out previous executed commands "saposcoll -k or kill -9 <pid>"
At the SAP level, you can try to figure out the responsible on the "security audit log" (SM20) who called tx "OS06".
Best regards,
Orkun Gedik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.