on 10-23-2014 7:20 PM
Hello experts,
there are 2 systems with different transport directory on the same host.
the systems have different product systems and therefore they can not have the same transport directory.
I noticed SUM does not like a transport directory other than /usr/sap/trans, for example /usr/sap/trans<sid>
I tried to copy one system to another host without creating directory /usr/sap/trans but only /usr/sap/trans<sid>
in such case SUM informs me that it is impossible to extract *.SAR files as it can not find /usr/sap/trans/EPS/in
I am confused. What shall I do in such case?
Should I create empty /usr/sap/trans with subdirectories
or should I rename /usr/sap/trans<sid> to /usr/sap/trans and change TMS properties?
Regards, Evgeniy
Hi
If you've moved to a new host why keeping you non standard naming convention.
Create an empty usr/sap/trans could make it, updating TMS conf also would be better (and do not forget the instance parameter DIR_TRANS)
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yves and Reagan,
thank you very mutch for your advice.
During the upgrade I changed transport directory to /usr/sap/trans
It is temporary solution but it helped me.
Regards, Evgeniy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Updating the TMS configuration with the correct transport directory would be the best option. For temporary purpose (upgrade) you can create a symbolic link
/usr/sap/trans -> /usr/sap/transSID
Regards
Reagan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.