Upgrade - Transport Directory Strategy

Hello All,
We are having the below 4.7 Landscape,
DEV -> QAS -> PRD
We are having central Transport Directory. /usr/sap/trans is present in PRD which is mounted to DEV and QAS.
Now, we are doing DEV Upgrade.
So, we have created a Temporary Development DVP for 4.7 (which is a copy of DEV) so that we can continue our 4.7 Developments. Basically a approach of Dual Landscapes for Upgrades, one for 4.7 and one for ECC6.
Now, DEV has its local /usr/sap/trans, while we have mounted /usr/sap/trans(of PRD) to DVP. So new 4.7 Landscape is
DVP-> QAS -> PRD
After I do my QAS Upgrade, 4.7 Landscape will be turned to a 2 System landscape. Because of H/W constraints we cannot have two QAS (one for 4.7 and other for ECC6).
My question is,
After I do my QAS Upgrade, should my QAS DIR_TRANS point to /usr/sap/trans of DEV or PRD?
I am planning to point it to that of DEV, we will have dual Central Trans Directories,
one for 4.7 Landscape (/usr/sap/trans in PRD) for DVP-> PRD
and the other for ECC 6 (/usr/sap/trans in DEV) for DEV -> QAS
What do I do after PRD upgrade? should my DIR_TRANS for ECC 6 PRD point to /usr/sap/trans of DEV ?
Thanks!

if you are upgrading in a parallel landscape , you really dont need to worry about the transport directory of the 4.7 landscape.
as soon as you upgrade the DEV , i guess you can have a DIR_TRANS pointing locally
and you can make that the Central transport directory for the ECC landscape
As i said earlier , you need to keep track of changes that are performed in the 4.7 landspace after the DEV upgrade and make sure they are recreated(if necessary) in the ECC landspace as part of the Dual maintanence.
As long as you keeo track of the changes that are happening in the 4.7 landspace and manage it approriately , you are fine.
Planning would be crucial.
Gerard

Similar Messages

Post Upgrade transport

We're currently in our upgrade project. I have a concern about our transport system after upgrading to ECC 5.0. Here is my scenario. We are currently upgrading from 4.6C to ECC 5.0. All systems are central installations no app servers. Production server consist of PRD. Second server contains DEV and QA. The transport directory is shared between these server.
Upgrade landscape is on another server containing a Dev 5.0 and QA 5.0 system. Our go live plan is to upgrade PRD after testing on QA 5.0. I will manually add post upgrade transports to PRD and then import. My question is, will I run into any problems by manually adding the transports to PRD?
Yes, I know 6.0 is the better upgrade version but it's a long story.
Thank you in advance.

Hi Martin,
What do you mean by post upgrade transport if it is SPDD & SPAU fixes then for this you will get option during the upgrade to add a single transport request.
If you are talking @ the development happening into DEV & QA system during the production system upgrade the you just need to keep track of the transport sequance and need to import in a same sequance in the PRD after the upgrade
Hope this will help you, do revert if you need any more info.
Best Regards,
Sachin.

UNIX permissions to NFS transport directory

I have upgraded lately to ERP 6.0 on HPUX /Oracle 10.
I have installed a NFS directory /usr/sap/trans .
When I release a transport request the owner is unknown (110) and the group (109).
The Productive system can see the file but has no access to it.
If I change the owner (chown) everything works fine.
What I have to do fix it ?
It sounds to me , there is a UNIX file that allows to insert shared users.
Thank you.

Hi,
the SIDadm user of DEV need to be domain user where you can provide him necessary access on the usr/sap/trans and same should be with Production, if the user was local only to DEV/PRD system then the DEV/PRD system trans directory cannot recognize and validate the permissions of SIDadm user.
You have to mount the usr/sap/trans of PRD onto usr/sap/trans of DEV so that what ever releases happens they will come and sits PRD trans directory and can be accessed by PRD.
Even when you mount the transport directory of PRD onto DEV, you should include the DEV system as trusted in PRD and viceversa.
Then this should work.
Regards...........
Edited by: Sita Rr Uppalapati on Jan 13, 2009 1:06 PM

CS4 UPGRADE INSTALL DIRECTORY VISTA 64 NOT x86

Hi all,
I would like to know if its safe that my CS4 Master Collection upgrade installation directory was in Program Files instead of the usual Program Files (x86)? Everything is working fine, however CS3 Master Collection applications are still installed and working normally (isn't that strange?) and of course the plugins I had installed in CS3 are not available in CS4. I don't mind that much that CS3 is still installed, I know it has happened to others, however it is a real drag that my plugins are not available. Should I uninstall the upgrade and reinstall in the Progam Files (x86) directory instead? Your comments would be much appreciated.
Nikos

Thanks for your response Bob. After a few hours (and an uninstall and reinstall on one computer) I realized that even though the directory location I was prompted to install to during installation was different than usual, the applications still wound up in the right place. All the 32 bit in the x86 folder, and Photoshop 64 verision in the regualr program files folder on my vista 64 platform. I discovered this on one of the other computers that I installed on but did not proceed to the uninstall phase. I still unfortunately had to re-install all my plugins and put them in the media core folder but for CS4. This was such a big hassle especially with some of my plugin suites that install one by one.
I still haven't researched the subject of uninstalling CS3, which I will probably attempt next week. Of course I am not going to try it until I have researched the subject in greater detail because I found some other users saying that uninstalling CS3 when you have used an upgrade option to CS4 is dependant on some CS3 files and after the uninstall of CS3 all was NOT working properly. Thanks again for your input. At least for this week I am already editing and enjoying CS4.

Shared transport directory best practices?

Does anyone have any documentation / knowledge on using a shared transport directory - ie, BI, R3, SolMan, etc in the same '/usr/sap/trans/cofiles + data directories, or is it preferred to keep them separate?
Currently, our R3 system shares one transport directory across the landscape, but BI, SRM, and Solution Manager do not. While thinking about giving each of them their own shared directories (all BI systems share a directory, all SRM system share a directory, etc), I wondered if the preferred method is to have them all share a directory.
I would appreciate any input, thank you.
~TJ

There are different philosophies here, but mine is:
Keep them separate so that a transport does not accidentally get moved to the wrong system. I know that with QA worklist and workflow and other tools that can be incorporated to allow this to not happen, but there is always a chance that a transport gets approval but goes to the wrong system, as in SAP fixes.
Hope this helps.

Common Transport Directory Migration

Our ERP 6.0 system is running on Windows 2003 Server 64 bit. The default install created a separate transport directory on each CI host. As a result users do not have log information of their transports into the PROD system, from the DEV or QAS systems. Currently they have to log into each instance to get their transport log information from the transport organizer.
I have read the online help and reviewed the SAP Notes on creating a common directory however I have not found any solid information to assist migrating/merging an already existing TMS setup. .
I have created the following check list in preparation to merge the separate transport directories into a common transport directory. Is there anything I missed?
1. Schedule maintenance to ensure Business analysts/Developers are out of all ERP systems.
2. Backup the entire \usr\sap\trans directories on DEV, QAS and PROD before beginning.
3. Update the TMS Domain Profiles for each respected system with the common directory path of the Transport Domain Controller. In our case it is the Dev server.
DIR_TRANS = \\hostname\sapmnt\trans
4. Merge the following QAS directories into the respected DEV directories (Confirm to overwrite existing files)
\usr\sap\trans\cofiles
\usr\sap\trans\data
\usr\sap\trans\logs
5.Repeat with the PROD directories into the respected DEV directories (Confirm to overwrite existing files)
\usr\sap\trans\cofiles
\usr\sap\trans\data
\usr\sap\trans\logs
Te goal is to insure that the delta changes between PROD, QAs & DEV are fully merged.
Common Transport directory
[http://help.sap.com/saphelp_erp60_sp/helpdata/EN/de/6b0da5f34d11d3a6510000e835363f/frameset.htm]
Thanks,
Jon Sells

We tried to implement this migration of the common transport directories and it was not successful. We ended up restoring back to the individual EPS directories.
What happened is that the QAS Queues did not reflect all the correct transports. (Yes, Siddhesh, I did as you said) In addition the add to buffer (crooked arrow) not longer functioned for newly released transports from DEV.
Does anyone have a white paper or SAP Note that would help on Migrating a common Tranpsort directory for Windows? Our Developers & Analyst do not like having to logon to each system to see view the transport logs. They are under the impression that they shoul be able to use SE10 in DEV and see the transport/import logs.
Thank you
Jon Sells

Change STMS transport directory

Hi gurus,
I have a High Availability SAP ERP system (SAP ECC 6.0) as PRD server. We used an old server for DEV system (Host name = sapdev). These two servers belonged to a STMS domain.
Recently we made homogeneous system copy and created a new Development (PRD copy) system to a new server. the new servers host name is AthinaDEV. We created a new STMS domain, joining the new DEV and PRD systems. The problem is that transport directory in PRD seams to be
sapdev\sapmnt\trans\ and in DEV seams to be
athinadev\sapmnt\trans\. In both servers in Transport Tool I have configured TRANSDIR as
athinadev\sapmnt\trans.
How can I change the transport directory to PRD to look
athinadev?
Thanks in advanced

OK,
I added the profile parameter DIR_TRANS with the correct path to both systems and now both systems use
athinadev\sapmnt\trans as transport domain. All seems to be correct now (all checks return success) but I can't transfer any request.
For example: I have created a test ABAP program. I have created a request for that program. I released the request from SE11 transaction succesffully. But when I use STMS transaction I have the following situation: in import overview I can see both systmes and 1 request waiting. When I double click on PRD to enter to import queue the list is empty.
I have cheked the permissions on trans folder and seems to be ok (prdadm has corrrect permissions).
The two systems has connected with transport routes.
Can anyone help me find the solution?

Compare upgraded transports

Hi Experts,
iam wrking on an upgradation from 4.7E to ECC6.0,
my task is to check the upgraded transports and compare the objects in DEV and QAS (quality) systems using the tranport number, i have a plan to check every transport no in SE01( transport organizer) and compare the obejcts in both systems.
now my query is the procedure which iam following is currect or is there any trascation codes to compare the objects and request in both DEV and QAS systems? if yes please explain in detail.
Thanks in advance
regards
neeru
Message was edited by:
neeru

I still don't know what you are trying to do
The normal way would be:
- Upgrade your DEV system
- Do SPDD during and SPAU after the upgrade and create transports for changes
- Upgrade QAS
- BIND the transports into the upgrade
- check if everything worked
- use the same transports for PRD
I don't know what you want to "compare" between your DEV and QA...
Markus

Central transport directory

Dear all,
we are running ecc 6.0 (v5r4m0), with central transport directory.
How can i switch to local transport directories.
Thanks
Imran Hasware

Hi Imran,
ok, if you don't know how to remove and add links with RMVLNK/DEL or ADDLNK then you should not change anything - otherwise it it 100% sure, that everything is destroyed afterwards
You are having a totally different problem as you write:
/usr/sap/trans/tmp/****.LOC file. already in use.
=> there is a semaphore file still there, that shows, that a TP is running - most likely since 3 days, since you are facing these issues.
If no tp is running anymore, this is an error and should be deleted manually. This kind of file is there by purpose so that the other TPs wait in critical pathes of other TPs. This happens in unshared trans dirs the same way ...
=> you should delete it and import 1 or 2 TPs first and see all is fine - then you can import your 30 TPs in one step - exactly because of these kind of files, it CAN be imported in parallel and will not crash the system.
(unfortunately this process sometimes gets out of sync ...)
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

Cleaning Up the Transport Directory

Dear All
I want to clear the old files from the trans directory, for the same, i exectute the command on Dos prompt,in
Windows
in BIN folder
tp check all
it generate following error
tp version is :- 372.04.57 (release 700, unicode enabled)
kernel release 700
This is tp version 372.04.57 (release 700, unicode enabled)
E-TPSETTINGS could not be opened.
EXIT
Error in TPSETTINGS: transdir not set.
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
error in transportprofil (param missing, unknown,...)
the Transport tool setting, the parameter
TRANSIDR is set
ides\sapmnt\trans &
DIR_TRANS value is
ides\sapmnt\trans
so please suggest me How to Cleaning Up the Transport
Directory
Thanks
Ganesh

Hi Ganesh,
Please go through the below links.
Import of a request failing : ERROR: connect failed due to DbSL load lib fa
how to add request in the buffer
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/tp-finished-with-return-code-208-1433190
http://www.sapfans.com/forums/viewtopic.php?f=12&t=67602
Re: Import of a request failing : ERROR: connect failed due to DbSL load li
-Srini

Same transport domain. different transport directory, possible?

Hi SAP folks,
A quick query, I work on multiple systems within a single SAP transport domain. Recently we have requirements to move 2 non-ABAP systems to a different transport directory while keeping the rest intact.
The reason for this is we are doing CTS+ for the 2 non-ABAP system and do not want to share the transport directories for the rest of the ABAP system.
Please advise if this can be done and how?
The following link for SAP suggested that it's possible but stop short of how to do it.
http://help.sap.com/saphelp_nw04/helpdata/en/c4/6045377b52253de10000009b38f889/content.htm
Anyone done similar setup? care to share?
Thank you.
Regards,
Jansen

Hi,
You can do this very well. First you should remove the two systems that you wanted to configure for CTS+ from your existing transport domain. To do this, login to your existing transport domain controller and delete the systems you wanted to remove from transport domain.
To perform this:
STMS --> Overview -> Systems -> < choose the system u want to delete> -> SAP Systems -> Delete. Confirm the deletion and save and activate the changes made to ur configuration.
And then add your Non-ABAP systems you wanted to configure for CTS+ using the domain controller you decided for CTS+.
I hope this help you to perform your action.
Best Regards,
Vasanth Govindaraj

Common transport directory configuration

Dear Gurus,
I installed ECC6.0 sr3 (dev and quality on the same server) windows 2003. Production server on seperate server. Now I want to configure common transport directory.
For dev and qas using same transport directory beacuse they are in the same server.
But production server is having seperate transport directory.
Is it compulsory having the common tranport directory.
Can Any body give the steps to add the production server in the same tranport directory.
Regards
Rao.

Is it compulsory having the common tranport directory.
No, it is not compulsory.
You can use STMS tcode to configure the same.
For further information, please go through the below link:
[Transport Management System|http://help.sap.com/saphelp_erp60_sp/helpdata/EN/44/b4a0137acc11d1899e0000e829fbbd/frameset.htm]
Regards,
Faisal

Easiest way to upload a transport file in the transport directory.

Hello all,
Do you know what is the procedure to upload a transport file in the transport directory in the process of manually installing OSS Notes?
Thanks in advance for your help,
Luis

Hi Luis,
Try to go through transaction SNOTE for that.
You can check also http://scn.sap.com/blogs/tyronemapp/2012/05/08/how-to-manually-import-transports-into-sap-without-using-command-line-tp , a nice blog post from Mapp Tyrone on the subject.
Take care,
Ricardo

Unable to use global transport directory

Hi,
I have a 3 system SAP landscape consisting of DEV, QAS, PRD. I configured TMS and put all three system into the same transport group. DEV and QAS can shared the same transport directory residing in DEV. However I am unable to get PRD to use the global transport directory. PRD is always using its transport directory. How can I allow PRD to use the global transport directory?
Rdgs

Hi,
The transport directory is shared out which explains why QAS is able to use the same transport directory. DIR_TRANS in PRD points to local transport directory and not the shared transport directory. Is there really a need to set DIR_TRANS parameter if TMS is configured? In QAS, I don't see DIR_TRANS being set in the instance profile.
I did tried setting DIR_TRANS in PRD however the system reported the parameter as unknown.
BTW, PRD is a copied from another system. We migrated the old PRD to a new server.
Rdgs

App Server Does not recognize the transport Directory

We have added a new server in the production system , but this server is not able to recognize the transport directory ,
In the instace profile , this parameter is set as below
DIR_TRANS =
bp1tulap139\sapmnt\trans
When i check the profile it throws a warning
W:DIR_TRANS directory
bp1tulap139\sapmnt\trans does not exist
Even the transport Directory
bp1tulap139\sapmnt\trans
is mounted on the server but still I am getting this error .
Please help

Oh man - that is Windows Security basics.
I am wondering how people can try to install and administrate enterprise level applications without this knowledge.
you may try to create SAPSERVICE<SID> as a local user on the machine where the transport directory is stored on and give it the same password on this machine. After that add it to the local SAP_LocalAdmin group.
After that the access should work (if both servers are member of the same workgroup).
peter

Upgrade - Transport Directory Strategy

Similar Messages

Maybe you are looking for