Release of a transport does not copy file to other system

[Former Member]

Hi All

I am struck with an issue. When I release a transport request from my DEV server, The corresponding files donot get copied to the local transport directory of QAS system, resulting in the non listing in the import queue of the QAS system.

I have checked the mentioned

1. STMS configuration is all active and all nodes are attached to the domain controller (DEV) with all green buttons

2. Single global transport group is configured for all the systems

3. QAS server can access the global transport directory in DEV system

4. RFC connection to QAS server from DEV server is fine

5. RDDIMPDP is scheduled in 000 client of DEV system through DDIC using Report RDDNEWPP

6. RDDIMPDP is scheduled in 000 client of QAS system through DDIC using Report RDDNEWPP. However, in SM37, the schedule does not get displayed.

7. The /sapmnt/sap/trans directory of QAS system is writable

8. /usr/sap directories of DEV and QAS system is shared as saploc and sapmnt

Any ideas of what could be the error.

Regards

Lokesh

[volker_borowski2 · Accepted solution]

>

> 2. Single global transport group is configured for all the systems
> 
> Lokesh

Hi,

All Systems belonging to the same transport group must share

the same DIR_TRANS. You need to setup diffrent Groups, if you like

to use a local transport directory.

WARNING: When using diffrent groups, but DIR_TRANS on these systems

points to the physical same directory, your transport files will get damaged

when trying to operate them !!! Read the documentation carefully to know

about the pitfalls of local transport directories.

Volker

[Former Member]

The DIR_TRANS and TRANSDIR were pointing to different directories. I have set up local transport directories now and created new transport group for all the systems. Have set DIR_TRANS and TRANSDIR to point to local directories.

The system has started working now, hence closing the message. Thanks to all for the suggestions

Lokesh

[Former Member]

Hi Lokesh,

Please check ur TR, whether its created as a local request or target system given in the request..

if its created as a local TR thn log will not be there. please check the log file also.

In this case again assgin the released TR with another TR (TR copy) as a workbench request and release the same.

With Regards,

Senthil Kumar.C