cancel
Showing results for 
Search instead for 
Did you mean: 

Mounting A Common Transport Directory in SAP Transport Config

Former Member
0 Kudos

Hi Gurus,

I'm newbi to Transport in the SAP. As per the documentation available, We have opted to QA as Domain Controller. For Initial Configuration, first I have started the NFS services on each of the Server. Also, I have make entries at /etc/hosts file of each server for the IP of the rest of the systems and has made the following entry to the /etc/exports file of the Domain Controller :

/usr/sap/trans <ip of DEV>.domain.com(rw,insecure,no_root_squash,sync

/usr/sap/trans <ip of PROD>.domain.com(rw,insecure,no_root_squash,sync)

Then at each of the machines EXCEPT Domain Controller :

#] exportfs –a

#] mount < ip of Domain controller > :/usr/sap/trans /usr/sap/trans

As I understand, through this mount command I am making /usr/sap/trans available to DEV and Prod System 'cause, my transport directory is common across all the three system and I don't need to give this command at the Domain Controller..

- as Domain Controller's own /usr/sap/trans is obviously available to itself.

Pl. correct me if I'm wrong in this.

Beside this, on Linux the command ' chkconfig --list nfs' should have output :

nfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off

But, on my Domain Controller, this command has different output :

nfs 0:off:1:off: 2:off 3:off 4:off 5:on 6:off

i.e. 3 and 4 remains off , whereas it must be in 'on' state.

So, how to solve this error at the OS Level.. ?

As I am getting ' TMS Configuration inconsistent' Error Message ..I want to make sure that my initial configuration at the OS level is correct.

Although I have include the DEV and PROD in the Domain Controller,

the problem is my Import Queue ( after releasing the request ) remains empty.

Useful answers will ALWAYS be rewarded without failure.

Many Thanks in Advance,

- ISHAN

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

This is all the basic config we need for transport. Thanks Guys!

Former Member
0 Kudos

The process I used to use to make an NFS share available was similar. Just update the hosts file with your remote systems and then add the domain names of those systems to the exports file (you can also enter the IP addresses). Restart your local NFS daemons to invoke the updated exports file (there is also a way to reload the configuration from the command line) running something similar to '/etc/init.d/nfs restart'.

On the DEV system, update your /etc/fstab file so it knows to mount a remote NFS share (add a line like this: server:/usr/sap/trans /usr/sap/trans nfs ) save, exit and run 'mount -av' to mount all the partitions listed in the fstab file (an error should appear if there is an issue with mounting the NFS share. Finally, run mount with no flags to view which partions were mounted.

Hope that helps.

J. Haynes

Denver, CO

Former Member
0 Kudos

I don’t think QA is the best system for configuring Domain Controller. It will be refreshed from PRD periodically which will wipe out your TMS configuration. You need to configure it over and over

Thanks

Prince Jose