cancel
Showing results for 
Search instead for 
Did you mean: 

the transport request is running all the time, what is the problem

Former Member
0 Kudos

I have a transport request which can transport from DEV to QAS successfully ,but failed when the request transport to PRD, I found the request running for several hours. I do not know what the problem? how can I check this problem?

need your help thanks

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member1351727
Active Participant
0 Kudos

Hi

The background job Rddimpdp is not scheduled in the system for client 000...And you want to investigate what happend to the job..

The background job details are kept in table TBTCO..So if you goto SE16 and try to choose the fields which are of your interest..as it(this table) has lot of fields. And in this we have fields like last run time,scheduled by,last job change time etc.So with the above information i hope you will be able to get the information you want.

And if everything is fine ..the backgrouns job alone can vanish someone manually might have done done something ..and that can be found out by above investigation on the table.

Hope this info helps...

Regards

Vani

Former Member
0 Kudos

thanks for the messages you give, I will try to investigate the real reason as you say.

Former Member
0 Kudos

oh, for this problem , I look over the slog then I find messages like that:"background job RDDIMPDP is not scheduled. Please run report RDDNEWPP"

so I go to client000 in PRD system to run RDDIMPDP using se38 . Finally , the transport to PRD can complete successfully. my tranport system is OK, now.

In fact , it is the problem about "RDDIMPDP" in client000 , I do not know why "RDDIMPDP" do not work? how can I investigate?

thanks

Edited by: victor on Jun 26, 2008 4:56 AM