permissions and owner for /usr/sap/trans & /usr/sap/trans/*

[ashish_vikas]

Hello friends,

We have installed a 3 system landscape and are having NFS mounted /usr/sap/trans common for transport. We are facing problem related to file permission..

Currently trans directory is owned by devadm:sapsys but after releasing a request from Dev, test system do not find correct permissons for that files. When we go to trans directory from Test system, it shows group owner as 203 instead of sapsys.

Permissions are correct as per : http://help.sap.com/saphelp_nw70ehp2/Helpdata/EN/0a/0a2e39ef6211d3a6510000e835363f/content.htm

After changing permissions manually, transport import work fine.

Can you please suggest something.

Regards

Ashish

[former_member189725 · Accepted solution]

This should be the permission and ownership of the transport directory

drwxrwx--x   root   sapsys   trans

For sub-directories under the trans directory , permission and ownership should be

drwxrwx--x    root   sapsys	bin
drwxrwx--x    root   sapsys	buffer
drwxrwxrwx   root   sapsys	cofiles
drwxrwxrwx    root   sapsys	data
drwxrwx--x    root   sapsys	EPS
drwxrwx--x     root   sapsys	etc

drwxrwx--x   root   sapsys     log

drwxrwx--x    root   sapsys	sapnames
drwxrwx--x    root   sapsys	tmp

The sapsys group id in /etc/group should be same in all the systems of the landscape.

Regards

Ratnajit

[ashish_vikas · Accepted solution]

yes, its not same.. but what should i do now. Is it safe to change and how?

Development System :

cat /etc/group

sapsys:!:203:ds1adm,ts1adm

test system :

cat /etc/group

sapsys:!:206:t62adm,ts1adm,ds1adm

Regards

Ashish

[JPReyes · Accepted solution]

Hi Ashish,

You have 2 options.

1st. Do a homogeneous system copy and fix the group while running the copy.

2nd. Stop the system, change the group and you'll have to check every directory, file and filesystem to make sure group ownership is correct. Its a heavy task but needed. I never had the need to do this so extra tasks might be needed

Regards, Juan

[former_member189725 · Accepted solution]

If you OS is AIX , bring down the applications running.

Then using SMITTY , change the group ID for sapsys. This should consistently update the group ID if it not used in the system for any other group.

For any other OS , check the relevant system admin tools.

Do not change manually in the file /etc/group.

Regards

Ratnajit

[Former Member · Accepted solution]

You can also do the following as workaround: create additional group (for example, sapsys2) with group id equal to group id of sapsys group on development system (in your case 203) if this id is not used and assign <sid>adm user from test system to members of this new group (sapsys2).

Regards

Roman

[JPReyes]

That is because <sid>adm user in the different systems have different user or group ID's at OS level check /etc/passwd and /etc/group. Ideally all user and group ID's should be consistent to avoid this issues.

Regards, Juan