Sie sind auf Seite 1von 17

Background job RDDIMPDP could not be started or terminated abnormally.

Unknown User asked Jun 12, 2003 | Replies (26)

Hi : I Have a problem with STMS transaction. When I want to transport a order the system don't work. The status shows a message : "order in execution" but the changes was made . The PCT log says

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.

(This warning is harmless if no further warnings follow.)

Can You help me please ? Thank in advance

Alejandro
Answer this question

Popular White Paper On This Topic

PDF Comparison Guide: Adobe Acrobat vs. Foxit Phantom PDF

26 Replies
0

Juan_M_Naranjo_A replied Jun 12, 2003

Please make sure you should have the scheduled job

RDDIMPDP with event start , this can be start with

RDDNEWPP.

After that, please follow the recommendations from the attached

SAP notes 71353, 26966 and 358813.

-----Mensaje original----De: Alejandro Attonaty via sap-r3-basis [mailto:sap-r3-basis@OpenITx.com]

Enviado el: Jueves, 12 de Junio de 2003 02:22 p.m. Para: Juan Manuel Naranjo Asunto: [sap-r3-basis] Background job RDDIMPDP could not be started or terminated abnormally.

Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp

Hi : I Have a problem with STMS transaction. When I want to transport a order the system don't work. The status shows a message : "order in execution" but the changes was made . The PCT log says

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.

(This warning is harmless if no further warnings follow.)

Can You help me please ? Thank in advance

Alejandro

*Archives: http://www.http://www.OpenITx.com/g/sap-r3-basis.asp/g/sap-r3-basis.asp

*Unsubscribe: mailto:leave-sap-r3-basis@openitx.com *Terms of Use: http://www.ittoolbox.com/help/termsofuse.htm

*Copyright (c) ITtoolbox and message author. No redistribution.


0

Unknown User replied Jun 12, 2003

<FONT face=3D"Default Sans Serif, Verdana, Arial, Helvetica, sans-serif" size=3D2><DIV>What says log of job RDDIMPDP?<br /> </DIV><FONT color=3D#990099>-----"Alejandro Attonaty via sap-r3-basis" <sap-r3-basis@OpenITx.com> wrote: -----<br /> <br /> </FONT>
0

User82103 replied Jun 12, 2003

Log on to client 000 and restart the job make sure you choose "*" under event and abap RDDIMP* under abap via sm37.

Thanks, Brian
0

Unknown User replied Jun 12, 2003

Hi, Plz run job RDDNEWPP to schedule RDDIMPDP...to on regular interval.

Check the logs to find out why the error occured before you schedule job RDDNEWPP. Good luck.

Regards, Imran

P.S. if RDDIMPDP not working, then plz send the further details so that I can help you out

White Papers and Webcasts


Popular

10 Things you Should Know About Website Security Related The Keys to the Kingdom: Limiting Active Directory ... 2011 Trends Report: Customer Relationship Management 10 Critical Sales Management Reports that Salesforce.com ... More White Papers 0

jim crissman replied Jun 12, 2003

More than likely one of 2 scenarios is happening:

1) your RDDIMPDP job(s) have failed or are not working 2) you have so many batch jobs running at once that RDDIMPDP cannot get batch processes

Check the status of your scheduled RDD* jobs in SM37 (you'll need to enter an * in the "or start after event" block) and give about a 24 hour time span. You should see a job for client 000 and one for each other client, e.g.

Job name Scheduled Released Ready Active Finished Cancelled

RDDIMPDP X RDDIMPDP_CLIENT_500 X RDDIMPDP_CLIENT_520 X RDDIMPDP_CLIENT_530 X RDDIMPDP_CLIENT_540 X RDDIMPDP_CLIENT_550 X RDDIMPDP_CLIENT_620 X RDDIMPDP_CLIENT_900 X

If they're not there, you'll need to reschedule them.

Also, run SM66 and look at your open batch processes and see if you have the BTC processes loaded up.

Regards, Jim

"Alejandro Attonaty via sap-r3-basis" <sap-r3-basis@openitx.com> 06/12/2003 06:22 PM Please respond to sap-r3-basis

To: Jim Crissman/Raleigh/IBM@IBMUS cc: Subject: [sap-r3-basis] Background job RDDIMPDP could not be started or terminated abnormally.

Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp

Hi : I Have a problem with STMS transaction. When I want to transport a order the system don't work. The status shows a message : "order in execution" but the changes was made . The PCT log says

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. (This warning is harmless if no further warnings follow.)

Can You help me please ? Thank in advance

Alejandro

*Archives: http://www.OpenITx.com/g/sap-r3-basis.asp *Unsubscribe: mailto:leave-sap-r3-basis@openitx.com *Terms of Use: http://www.ittoolbox.com/help/termsofuse.htm *Copyright (c) ITtoolbox and message author. No redistribution.
0

Unknown User replied Jun 12, 2003

People : Thanks for your responce !!! I was runned job RDDIMPDP and the status is in : " REQUESTED WAITING TO BE IMPORTED "

but when I want to imported a order the system display a message : " SET VERSION FLAG " and it don=B4t work... I'm sorry !! my english is little !!! Thanks !!

-----Mensaje original----De: Jim Crissman via sap-r3-basis [mailto:sap-r3-basis@OpenITx.com] Enviado el: Jueves, 12 de Junio de 2003 04:53 p.m. Para: Alejandro Asunto: [sap-r3-basis] Re: Background job RDDIMPDP could not be started or terminated abnormally.

Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp

More than likely one of 2 scenarios is happening:

1) your RDDIMPDP job(s) have failed or are not working 2) you have so many batch jobs running at once that RDDIMPDP cannot get

batch processes

Check the status of your scheduled RDD* jobs in SM37 (you'll need to enter

an * in the "or start after event" block) and give about a 24 hour time

span. You should see a job for client 000 and one for each other client,

e.g.

Job name Scheduled Released

Ready Active Finished Cancelled

RDDIMPDP X RDDIMPDP_CLIENT_500 X RDDIMPDP_CLIENT_520 X RDDIMPDP_CLIENT_530 X RDDIMPDP_CLIENT_540 X RDDIMPDP_CLIENT_550 X RDDIMPDP_CLIENT_620 X RDDIMPDP_CLIENT_900 X

If they're not there, you'll need to reschedule them.

Also, run SM66 and look at your open batch processes and see if you have the BTC processes loaded up.

Regards, Jim

"Alejandro Attonaty via sap-r3-basis" <sap-r3-basis@openitx.com> 06/12/2003 06:22 PM Please respond to sap-r3-basis

To: Jim Crissman/Raleigh/IBM@IBMUS cc:

Subject: [sap-r3-basis] Background job RDDIMPDP could not be started or terminated

abnormally.

Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp

Hi : I Have a problem with STMS transaction. When I want to transport a

order the system don't work. The status shows a message : "order in

execution" but the changes was made . The PCT log says

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.

(This warning is harmless if no further warnings follow.)

Can You help me please ? Thank in advance

Alejandro

*Archives: http://www.http://www.OpenITx.com/g/sap-r3-basis.asp/g/sap-r3-basis.asp

*Unsubscribe: mailto:leave-sap-r3-basis@openitx.com *Terms of Use: http://www.ittoolbox.com/help/termsofuse.htm

*Copyright (c) ITtoolbox and message author. No redistribution.

*Archives: http://www.http://www.OpenITx.com/g/sap-r3-basis.asp/g/sap-r3-basis.asp

*Unsubscribe: mailto:leave-sap-r3-basis@openitx.com *Terms of Use: http://www.ittoolbox.com/help/termsofuse.htm

*Copyright (c) ITtoolbox and message author. No redistribution.


0

Unknown User replied Jun 12, 2003

Plz check if RDDVERSL is in wait state in TXN sm37...if it is then release it.

Regards, Imran
0

Juan_M_Naranjo_A replied Jun 12, 2003

Check the notes that i send you in the previous MAIL.

What does your tp Log says ?

-----Mensaje original----De: Alejandro Attonaty via sap-r3-basis [mailto:sap-r3-basis@OpenITx.com]

Enviado el: Jueves, 12 de Junio de 2003 03:21 p.m. Para: Juan Manuel Naranjo

Asunto: [sap-r3-basis] Re: Background job RDDIMPDP could not be started or terminated abnormally.

Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp

People : Thanks for your responce !!! I was runned job RDDIMPDP and the status is in : " REQUESTED WAITING TO BE IMPORTED "

but when I want to imported a order the system display a message : " SET VERSION FLAG " and it don=B4t work... I'm sorry !! my english is little !!! Thanks !!

-----Mensaje original----De: Jim Crissman via sap-r3-basis [mailto:sap-r3-basis@OpenITx.com] Enviado el: Jueves, 12 de Junio de 2003 04:53 p.m. Para: Alejandro Asunto: [sap-r3-basis] Re: Background job RDDIMPDP could not be started or terminated abnormally.

Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp

More than likely one of 2 scenarios is happening:

1) your RDDIMPDP job(s) have failed or are not working 2) you have so many batch jobs running at once that RDDIMPDP cannot get

batch processes

Check the status of your scheduled RDD* jobs in SM37 (you'll need to enter

an * in the "or start after event" block) and give about a 24 hour time

span. You should see a job for client 000 and one for each other client,

e.g.

Job name Scheduled Released

Ready Active Finished Cancelled

RDDIMPDP X RDDIMPDP_CLIENT_500 X RDDIMPDP_CLIENT_520 X RDDIMPDP_CLIENT_530 X RDDIMPDP_CLIENT_540 X RDDIMPDP_CLIENT_550 X RDDIMPDP_CLIENT_620 X RDDIMPDP_CLIENT_900 X

If they're not there, you'll need to reschedule them.

Also, run SM66 and look at your open batch processes and see if you have the BTC processes loaded up.

Regards, Jim

"Alejandro Attonaty via sap-r3-basis" <sap-r3-basis@openitx.com> 06/12/2003 06:22 PM Please respond to sap-r3-basis

To: Jim Crissman/Raleigh/IBM@IBMUS cc:

Subject: [sap-r3-basis] Background job RDDIMPDP could not be started or terminated

abnormally.

Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp

Hi : I Have a problem with STMS transaction. When I want to transport a

order the system don't work. The status shows a message : "order in

execution" but the changes was made . The PCT log says

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.

(This warning is harmless if no further warnings follow.)

Can You help me please ? Thank in advance

Alejandro

*Archives: http://www.http://www.OpenITx.com/g/sap-r3-basis.asp/g/sap-r3-basis.asp

*Unsubscribe: mailto:leave-sap-r3-basis@openitx.com *Terms of Use: http://www.ittoolbox.com/help/termsofuse.htm

*Copyright (c) ITtoolbox and message author. No redistribution.

*Archives: http://www.http://www.OpenITx.com/g/sap-r3-basis.asp/g/sap-r3-basis.asp

*Unsubscribe: mailto:leave-sap-r3-basis@openitx.com *Terms of Use: http://www.ittoolbox.com/help/termsofuse.htm

*Copyright (c) ITtoolbox and message author. No redistribution.

*Archives: http://www.http://www.OpenITx.com/g/sap-r3-basis.asp/g/sap-r3-basis.asp

*Unsubscribe: mailto:leave-sap-r3-basis@openitx.com *Terms of Use: http://www.ittoolbox.com/help/termsofuse.htm

*Copyright (c) ITtoolbox and message author. No redistribution.


0

Unknown User replied Jun 15, 2003

Hi Alejandro, If you have been able to fix the prob...then plz let me know how you have done it. Thanks.

Regards, Imran
0

Mohan Gudeti replied May 12, 2008

Will anyone tell me how this issue was fixed?


0

Pedro Lopes replied May 12, 2008

I didn't read all the problem history, but here is my opinion about generic problem. RDDIMPDP and other jobs for transports are launched in background by event from TP that runs in operating system. First of all, see in SM37 if the job is there to run and if ther is work processes available for it to run. If the job is not in SM37, you should redefine it. For that, in productive client and in client 000 (in both) you should run report RDDNEWPP in

se38. This will redefine new jobs. Se also if there is no file system like /usr/sap 100% full... Regards, Lopes
0

Snowy

replied May 12, 2008

you look into SM37 for cancelled job and loo kat the job log. if you cannot find the job, run RDDNEWPP into client 000 and your productive client.
0

Robert Jessie replied May 13, 2008

Make sure DDIC user is not locked in PROD client and 000. Bob Jessie
0

sudhir yadav replied May 14, 2008

Check in the transport monitor whether any transport entry is there in execution. If there, delete the entry. Check the free space in /usr/sap/trans. And also check any .LOB or .LOC file exists in /usr/sap/tmp.

Sudhir Kumar Yadav SAP Basis Consultant


0

Ashutosh Awasthi replied May 14, 2008

Dear Sudhir, Try rescheduling the same job and run in immediately in production
0

Vills_Vedant replied Feb 17, 2009

Background job RDDIMPDP could not be started or terminated abnormally.


0

David Caddick

replied Feb 17, 2009

Hi Vilas, Do you have a new problem. Please give more information on this issue.

Are you seeing the error when you try to import Transport requests, or in the Job Log in Tx SM37? We can't really help without you giving more information. Regards
0

Snowy

replied Feb 17, 2009

Simply start program RDDNEWPP from clients 000 and your productive client. this will schedule your RDDIMPDP with proper values for you.
0

thecdog replied Feb 17, 2009

Run ABAP program RDDNEWPP from SE38 this will schedule to approprate job.
0

David Caddick

replied Feb 17, 2009

Hi Vilas, Have you re-run program RDDNEWPP in all you clients and are you still getting the "could not be started or terminated abnormally" message. If you are still getting this problem please provied the full job Log. and see if you also have a ABAP Short dump with Tx ST22. Regards
0

Vills_Vedant replied Feb 18, 2009

Hi caddick ...

Sorry ... here are some details ...

While doing STMS my request getting hang. And in logs it is showing that process RDDIMPDP terminated abnormally. And in SM37 same process is showing cancelled status without any logs.

I tried by log in client 000 and through se38 I executed prog. RDDNEWPP same process I repeated in client 500 but still it is showing In SM37 as cancelled status. And I can't able to transport requests.

I also tried by umount and mount of /usr/sap/trans .

Please guide. Regards, VILAS


0

David Caddick

replied Feb 18, 2009

Hi Vilas, Ok so mow please provied the full job Log. Also did you check Tx ST22 to see if you have any ABAP short dumps. Please also check you have the latest versions of programs R3trans and tp. I reciently had a problem and SAP told me to run program RDDNEWPP only using user DDIC. So logon to all clients with user DDIC and run RDDNEWPP again. Please provide feedback too. Regards
0

Vills_Vedant replied Feb 18, 2009

Hi Caddick

My problem has solved. The owner and group has been changed which not allowing to read/write the logs. I changed owner and group as SIDadm and sapsys as chown -R SIDadm:sapsys. OF Log dir.

Thanks for your response.

Regards

Vilas
0

David Caddick

replied Feb 18, 2009

Hi Vilas, Thank you for letting us know the problem is solved and the solution you used. That would have been a dificult issue for people in this group to indetify. Regards
0

Snowy

replied Feb 18, 2009

that is great news. it would be interesting if you would explain how you were able to troubleshoot that problem.
0
Zahoor-Bhat replied May 24

After tried all options, I have fixed the same issue by following below steps:

1. Stop all running tp jobs at os/sap level and remove existing entries in running import from SAP level by opening the running truck button.

2. Delete all entries from TRBAT/TRJOB/TPSTAT tables, TPSTAT table entries can only removed from BD level.

3. Delete existing RDDIMPDP and RDDIMPDP_CLIENT_<CLIENT#> jobs from SM37

4. Re-schedule the RDDIMPDP job from client-000 via DDIC by running RDDNEWPP report (Make sure you select job priority HIGH)

5. Re-schedule the RDDIMPDP_CLIENT_<CLIENT#> job from client-client#(400) via DDIC by running the same report (Make sure you select job priority HIGH)

6. Search these jobs from SM37 and assign Execution Target server and save them.

7. Start transport import again, it will work now and transport will finish with minutes rather than running for long time.

I hope above steps will be helpful for someone...

Reply
Show formatting options

Post Your Reply

Ads by Google