Transport problem

[Former Member]

Hi!

Here the history of problem. Some time ago we had a following landscape: server1 with system SANDBOX and server2 with system TEST. We moved system TEST to server1. Now we have two systems u2013 SANDBOX and TEST u2013 on server1. Server2 has now the system PRODUCTION.

The problem is that we canu2019t start up systems SANDBOX and TEST simultaneously. We get in log:

u201CWARNING: Background job RDDIMPDP could not be started or terminated abnormally. Please check that the R/3 system is running. Please check the system. Use transactions SM21, SM37, SM50. WARNING: (This warning is harmless if no further warnings follow.)u201D

And transport requests from TEST to PRODUCTION hang. I think we need to reconfigure transport from SANDBOX to TEST with saving transport between TEST and PRODUCTION. But how? What to see, what to change? Please help.

Thanks, Olga

[Ayax]

Your Test and Sandbox system are sharing same transport directory so why I would do is reconfigure the transport sytems in order to include Sandbox but with no transport routes going in or out of it. If this does not work I would try changing the transport directory for Sandbox.

Regards,

Ayax

[Ayax]

If you do not start the Sandbox server your transports work ok?

Are your Test and Sandbox instance numbers the same?

Regards,

Ayax

[Former Member]

If you do not start the Sandbox server your transports work ok? > Yes

Are your Test and Sandbox instance numbers the same? > No

Thanks, Olga

[Former Member]

Hi,

Is this issue resolved? if not, check in ST22 dump Analysys, it may likely give you this is due to Kernal program in "what happened section" can you check it up?

Reg, Venkat

[Ayax]

Hello Olga,

Can you explain how was your transport landscape before and after the server change, I mean, did you had a transport route between Test and Sandbox? is there a Development server? was your Production server moved or a new installation?

Regards,

Ayax

[Former Member]

No, we did not have transport between TEST and SANDBOX. SANDBOX was not included in transport chain TEST-DEV-PROD at all. And I think it is correct. We had normal transport TEST-DEV-PROD and have it now, but now TEST and SANDBOX are in one host, and attempt to start SANDBOX results to impossability of TEST normal work (TEST can't process transport requests).

Thanks, Olga

Edited by: Olga Trofileeva on Jan 19, 2009 10:35 AM

Edited by: Olga Trofileeva on Jan 19, 2009 10:39 AM

[Former Member]

Sandbox is a system which meant to be discard once you are done with it. Mostly it is out of transport route and any transports need to go to Dev, we have data and cofile moved to Dev.

[Former Member]

Hi,

Assuming like there is no transports happening between Sandbox and Test.

In this case, redefine the transport system and routes between Production and Test system.

Distribute and activate the systems across the network.

Hope it helps

Regards

KT

[Former Member]

Hi!

But Basis people say that it is normal to don't have transport between SANDBOX and other instances (DEV, TEST, PROD). Can your say from your own practice is it so?

Thanks, Olga

[Former Member]

Hi,

Re-configure your transport routes and update your systems landscape in tranport management system via transcation STMS.

And make sure you activate and distrube the new changes to whole landscape (Sandbox, Test & Production).

Hope this helps,

Kalyan.

[Former Member]

But is it possible:

first) to transport changes made in TEST to SANDBOX (to make TEST and SANDBOX the same)?

second) change transport once more to transport new changes made in SANDBOX to TEST?

That is - can we change transport routes many times? Is it normal situation?

Thanks, Olga

[Former Member]

Hi,

It is not normal. But you have PRD & Test systems moved (physically) that means system hostnames were changed. That requires a re-configuration of your transport routes, making sure your configuration in STMS matches to your physical systems in your landscape

hope this helps,

Kalyan.