Background job RDDIMPDP could not be started or terminated abnormally

[Former Member]

Hi,

System ruuning with very slow performance, also transports taking too long time to import.

I found some errors in SLOG , there are many entries " Background job RDDIMPDP could not be started or terminated abnormally"

As per SAP note 79518 , this standard job is not running properly. Do i need to reschedule this job in client 000 as ddic. Is there any conflict/effect for my prod system to trigger this job?

Do i need to schedule this job in all clients or only 000 is enough ?

WARNING: 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.)

WARNING: System QMS. Warning. 20061113154258 :

WARNING: 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.)

WARNING: System QMS. Warning. 20061113154759 :

WARNING: 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.)

WARNING: System QMS. Warning. 20061113155259 :

WARNING: 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.)

WARNING: System QMS. Warning. 20061113155800 :

WARNING: 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.)

WARNING: System QMS. Warning. 20061113160301 :

WARNING: 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.)

Thanks

Lisa

Any idea..

[Former Member]

sorry to make this thread live again

in case people have same problem as me

this problem appear when I lock DDIC user in client 000

and RDDIMPDP is triggered by DDIC user,

after change RDDIMPDP's user via SM37

the transport running smooth again

[Former Member]

Hi Dimas:

We have exactely the same issue since we lock DDIC in client 000.

How did you change RDDIMPDP job, once its not scheduled, but its trigered instead?

There's no "release" entry on SM37 for such job?

[Former Member]

Got it.

The trick to "see" RDDIMPDP job (in order to change the Backgroud User Name for Authorization Check from DDIC to another one), is to type "or after event" = *, on SM37.

[Former Member]

HI

Can you post the log of error, bcoz it can be related to SAPEVT.

Its log can be found in dev_evt.

SAP note 642464 - Profile file for the program sapevt

449270 - Job RDDIMPDP is not triggered by sapevt

and in some case get resolved by adding SID/system_pf=
hostname
parameter.

Regards

Arun.H

[Former Member]

Hi Lisa,

There was one such case for our quality sytem. All the jobu2019s in system getting aborted without error log .

We checked sm21 logs and found file system /sapmnt/SID full.

File system was cleared and job was scheduled in 000 client.

Hope it helps.

Thankks

Edited by: Chetna Verma on Nov 9, 2011 1:16 PM

[anindya_bose]

Hi Lisa

Login to 000 client and run a report RDDNEWPP from SE38 in dialog mode. Select the priority as 'A' for the job.

could you please check the entry in the table TRBAT ? if it contains any entry you can safely delete that from Sm30 and then re-run the transport.

Reards

Anindya

[Former Member]

HI Lisa,

Is this issue resolved? if yes please update the solution and close it.

Please check SM61 for background servers have been assigned.......

If not assign it and then check whether your jobs are running......

Regards,

Sravan

[Former Member]

I was facing the same issue and resolved it by running report rddnewpp in client 000.

Thanks a lot

[Former Member]

Hi Anindya,

Thanks for the tip is now working.

Roberto Lima

[Former Member]

Hi Anindya,

Your tip seems to be working.

But my import hangs in every phase. If I actively delete entries from TRBAT, the import is moving forward.

But this can't be the case. Any more tips?

Regards,

Uday

[shouvik]

Hi Uday,

Please check note number 12746 for this problem. Basically all you need to do is to stop any tp/R3trans process running on the OS level, move all .LOB or .LOC files from /usr/sap/trans/tmp to another location. Then restart the the process. Also refer to note 690449 and 132536 for more information.

Hope this solves your issue.

Best regards,

Shouvik Sarkar

[Former Member]

Hi Guys,

Some of possible reasons are already mentioned in this thread. There could be two other possible reasons for the same issue which we have encountered:

1) /usr/sap/trans directory permissions (while doing any transport tp program not able to write down anything in transport directory. so set the correct permissions for transport directory).

2) We have changed the Time Zone of SAP system and as well as at OS level (AIX 5.3) i.e. TZ env variable, but we didn't take a restart of SAP system and all RDDIMPDP throwing ZDATE_LARGE_TIME_DIFF. After restarting system everything went fine.

Regards,

Mukul SHarma

[Former Member]

I just had this same issue.

I discovered that the cause was because the program RDDNEWPP did not automatically set a schedule for RDDIMPDP to run repeatedly. Why was this?

More info here: http://sapbasis.stackexchange.com/questions/12/background-job-rddimpdp-could-not-be-started-or-termi...

[Former Member]

Try starting the job by executing the report RDDNEWPP, which will start the job RDDIMPDP

regards

Sudha

[Former Member]

Sometimes this will happen if something is wrong with the original install (the only time I have seen it do this). I was able to get around it by running the program "RDDIMPDP" on the foreground from se38. Do you get any error messages when you try to run it this way? Make sure you run it from client 000 as a user who has the right authority as well. You might need to run this program multiple times until you get the transport/support pack to work.

[JPReyes]

Hi Lisa,

Have you checked the logs??

<b>"Please check the system. Use transactions SM21, SM37, SM50."</b>

Regards

Juan

[Former Member]

Hi Guys... i have the same issue.. & my SPAM is stuck ... how can i fix this ....

[Former Member]

You need to start this job in 000 client as ddic, no need to start it in any other client.

Thanks

[Former Member]

I faced the same problem too... is it has any effect by /sapmnt ? since my /sapmnt folder is full and I don't know how to clean it...

the folder that make my /sapmnt full is /global folder under my/<SID> folder

if the problem comes because my /sapmnt full, which file on my /sapmnt/<SID>/global I can delete ??

also I had runn RDDNEWPP from client 000 using DDIC userID... but nothing happended, the same error still happened and the STMS tcode still shows "import running"

[Former Member]

Try to launch the trigger via SM64,in the SM37 what is the status of the job?

Regards,

Alfredo.