cancel
Showing results for 
Search instead for 
Did you mean: 

SAPOSCOL running then getting killed and running again!!!

Former Member
0 Kudos

Hi experts,

Well i have been trying to figure this out for a while

1)Saposcol stops showing message :'Shared memory not attached'

2) so i started it again

3) after few minutes it stops again with same message

Now the version of saposcol

saposcol -v

SAPOSCOL version COLL 20.95 640 - AIX v11.16 5L-64 bit 080318, 64 bit, single threaded, Non-Unicode

compiled at Aug 16 2008

NOw SAP system info

cwpdi11:cwpadm 79> disp+work|pg

-


disp+work information

-


kernel release 640

kernel make variant 640_REL

compiled on AIX 1 5 00538A4A4C00

compiled for 64 BIT

compilation mode UNICODE

compile time Nov 18 2008 22:07:55

update level 0

patch number 260

source id 0.260

Questions

1)Should i clean the shared memory and start it freshly again???

2) Is it because of version of OS coll....because i checked on other systems the version was 20.95??

Suggestions will be appreciated

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Ameya,

it seems there is a complete issue with Authorizations of saposcol.

change u r permissions like the below with the user root.

chown root saposcol

chgrp sapsys saposcol

chmod 4750 saposcol

eg:-rwsr-x---1 root sapsys XXXXXX Mar XX XX:XX saposcol

read the complete Note 19227 - (open newest saposcol) for the more information.

Hope that will helps you.

-Srini

Edited by: Srinivas Korva on Mar 23, 2009 10:36 AM

Edited by: Srinivas Korva on Mar 23, 2009 10:39 AM

Former Member
0 Kudos

Hi Ameya

You may have to release some memory for successful execution of SAPOSCOL.

SAPOSCOL generally stops or goes in IDLE status or even stops the write access in case it does not find available memory

Regards

Chen

Former Member
0 Kudos

Hi,

Also check the permisions of saposcol in exe directory

Regards,

Tajinder

Former Member
0 Kudos

Well here are the permissions

cwpdi11:cwpadm 73> ls -altr saposcol

-rwsr-x--- 1 cwpadm sapsys 1293585 Aug 17 2008 saposcol

these r the permission recommended by sap

Also 1 more question

cwpdi11:cwpadm 78> ipcs -ma|grep -i 4dbe

m 176029800 0x00004dbe --rw-rw-rw- cwpadm sapsys cwpadm sapsys 1 1870188 216270 216270 5:41:41 5:41:44 5:41:37

Are above permissions of saposcol???

Former Member
0 Kudos

Hi Ameya,

This can be the authorization isse of your <SID<adm user

Please change the owner to root

that means the permissions shlould be like

-rwsr-x--- 1 root sapsys 1293585 Aug 17 2008 saposcol

Group should be sapsys only

Regards,

Tajinder

Former Member
0 Kudos

Ameya,

It looks like permissions issue with the saposcol executable.

SAPu2019s recommendation is that SAPOSCOL be started under user root when you start your R/3 System.

Please find detailed information in the attached link below.

[http://help.sap.com/saphelp_40b/helpdata/EN/1f/8312264bc511d189750000e8322d00/content.htm]

Hope this helps.

Manoj

JPReyes
Active Contributor
0 Kudos

cwpdi11:cwpadm 73> ls -altr saposcol

-rwsr-x--- 1 cwpadm sapsys 1293585 Aug 17 2008 saposcol

these r the permission recommended by sap

SAPOSCOL needs permission 4755 in order to work correclty.

Regards

Juan

Former Member
0 Kudos

Hi,

We some times auth issues on OS level like these with SAPOSCOL with <SID>adm.

It can be cause of memory acquiring limitations for the users other than root too.

So we can run SAPOSCOL with root and group as sapsys.

Regards,

Tajinder

Former Member
0 Kudos

Hi

Stop saposcol and run command "cleanipc 99 remove" and restart saposcol.

Rahul

Former Member
0 Kudos

Hello Ameya,

Refer to Note 522901-it might be of use to you

I would recommend you to get the newest version of SAPOSCOL from marketplace

that might help

Rohit