SAPOSCOL is not running ? (shared memory not available)

[HJ1]

Hi,

I am getting this error

i have started the saposcol from os level and in

ps -ef | grep saposcol it is showing running

But when i call OS06

it is again showing the same error :

SAPOSCOL is not running ? (shared memory not available)

please help me ASAP

[Former Member · Accepted solution]

Hi Harish

Please check, if the permissions of the binary are correct:

sidadm 22> ll saposcol
-rwsr-x---   1 root       sapsys     2340936 Oct 30  2006 saposcol

Regards Michael

[HJ1]

HI Mich,

I am trying to open these

sidadm 23> file disp+work

Can not open

sidadm 24> file saposcol

Can not open

[Former Member]

Hi,

still look like authority issue,

read sap note Note 19227 - Open newest saposcol

regards,

kaushal

[HJ1]

HI Kushal,

Log File

interval 0 sec.

Collector Version:

Date/time 10.12.2007 07:33:26

Start of Collector

Contents of log file

HWO description

07:32:10 10.12.2007 LOG: Profile : no profile used

07:32:10 10.12.2007 LOG: Saposcol Version : [COLL 20.93 700 - V2.5.4 2006-12-04 HP-UX IA64]

07:32:10 10.12.2007 LOG: Working directory : /usr/sap/tmp

07:32:10 10.12.2007 LOG: Identified system as: HP-UX MADAP800 B.11.23 ia64 hp server Integrity Virtual MachinHP-UX

07:32:10 10.12.2007 LOG: Architecture identified as 64-bit

07:32:11 10.12.2007 LOG: Shared Memory Size: 1997812.

07:32:11 10.12.2007 LOG: Shared Memory was created by process:17748

07:32:11 10.12.2007 LOG: ==== Collector submitted. This is the parent process after fork.=====

07:32:14 10.12.2007 LOG: ==== Collector submitted. This is the child process after fork()=====

07:32:17 10.12.2007 LOG: Collector daemon started

07:32:17 10.12.2007 LOG: read coll.put Mon Dec 10 07:32:01 2007

07:32:17 10.12.2007 LOG: Collector PID: 17751

07:32:27 10.12.2007 LOG: Initialize Process Monitoring :

07:32:27 10.12.2007 LOG: Process Monitoring active.

07:32:27 10.12.2007 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/dev_proc

07:32:27 10.12.2007 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/

07:32:27 10.12.2007 LOG: The following processes will be monitored:

07:32:27 10.12.2007 LOG: Process: jlaunch-DSAPINFO=P30_30_dispatcher* for user: p30adm

07:32:27 10.12.2007 LOG: Process: jlaunch-DSAPINFO=P30_30_server* for user: p30adm

07:32:27 10.12.2007 LOG: Process: jlaunch-DSAPINFO=P30_30_sdm* for user: p30adm

07:32:27 10.12.2007 LOG: Process: jlaunch-DSAPINFO=S60_60_dispatcher* for user: s60adm

07:32:27 10.12.2007 LOG: Process: jlaunch-DSAPINFO=S60_60_server* for user: s60adm

07:32:27 10.12.2007 LOG: Process: jlaunch-DSAPINFO=S60_60_sdm* for user: s60adm

07:32:27 10.12.2007 LOG: Process: jlaunch-DSAPINFO=X40_40_dispatcher* for user: x40adm

07:32:27 10.12.2007 LOG: Process: jlaunch-DSAPINFO=X40_40_server* for user: x40adm

07:32:27 10.12.2007 LOG: Process: jlaunch-DSAPINFO=X40_40_sdm* for user: x40adm

[HJ1]

Hi Kushal,

I have already done these steps meane change owner and permission but still facing same error in tcode os06 and sto6

[Former Member]

Hi Harish

<i>I have already done these steps meane change owner and permission but still facing same error in tcode os06 and sto6</i>

Does this mean, the permissions were wrong in the beginning? Because you will need to restart saposcol after the permission change (and probably cleanipc/ipcrm the shared memory).

If you have already restarted saposcol, then please check if you have the correct IA64 or PA-Risc 32/64-bit saposcol. See Note 173160 - SAPOSCOL not running ? HPUX 11

Here an example from a 11.23 IA64 platform:

sidadm 22> uname -a
HP-UX localhost B.11.23 U ia64 xxxxxxx unlimited-user license
sidadm 23> file disp+work
disp+work:      ELF-64 executable object file - IA64
sidadm 24> file saposcol
saposcol:       ELF-64 executable object file - IA64

Regards Michael

[Former Member]

Hi,

provide saposcol log,

st06 -> operating system collector -> log file

regards,

kaushal

[HJ1]

Unix is HP-ux

We have more then 1 system in this server

[Former Member]

Hi,

The problem usually happen if you have several SAP systems with different

versions in one machine. Then we need to check from ST06 if SAPOSCOL is the

correct one for the system specified.

also check permission for user

just login in root.

and type in \usr\sap\SID\SYS\exe\run

ls -l saposcol = user must have execute rights check. if not give rights.

the correct permissions for saposcol look like this:

-rwsx- 1 root sapsys 1256030 DEC 12 2007 saposcol

You achive this with by running these commands as root:

chmod 4710 saposcol

chown root:sapsys saposcol

Otherwise, please patch the latest SAPOSCOL from SAP Service Marketplace.

regards,

kaushal

[Former Member]

Is there more than one Instance running on the same server? Usually it will be fine once you restart sap

thanks

Prince Jose

[Former Member]

Hi,

Which flavour of unix, you are having...

With regards

Sudha

[HJ1]

Hi Michle,

What shuld be the commond for that and the steps if you can send