background job is terminating frequently

[Former Member]

Dear All,

I am updating the sap abap patch sapka64012 in mysap ecc5 . At the time of updation it hangs and in system logs it is giving the below error

" Background job RDDIMPDP could not be started or terminated abnormally"

when I start the this service manually through ddic user in 000 client , patch is updating perfectly .

pl. help me . why this service is stoped again and again ?

[Former Member · Accepted solution]

Hi Sonal,

Check the free space in

/usr/sap/trans. And also check any .LOB or .LOC file exists in

/usr/sap/tmp.

Cheers

Deepanshu

[Former Member · Accepted solution]

Hi Deepanshu ,

Thanks for your reply , there is enough space is available and no .LOB and .LOC files are exist in tmp folder .

Pl. advice

[Former Member · Accepted solution]

Hi Sonal,

One of the reasons could be that there are multiple jobs running when the process chain runs and hence the job is getting cancelled.

The other reason could that the background user does not have the authorization for APD process now.

Can you set a wait time on the APD process and run the chain in background mode(not immediate) and check if it works.

Cheers

Deepanshu

[Former Member · Accepted solution]

Hi Deepanshu,

Can you little bit brief it ?

How to check the APD process and how to set its time ?

Thanks for your help .

[Former Member · Accepted solution]

hi ,

sonal check for the long running jobs in SM37 * ,* ACTIVE from past 10 days chk from how long they are running and check the priority if they are not rquired kill them,

SUPPOORT PACK will hang when back ground jobs are not available if want u can go to sm51

and chk for the background jobs availability .if they are not availabile then u have to call any long runnning job ,

then your sp will run.

Regards

Zia

[Former Member · Accepted solution]

Hi Sonal,

Please check for

tp showbuffer <SID> pf=\usr\sap\trans\bin\TP_DOMAIN_<SID>.PFL (at OS level ).

Also check for RDDGEN0L job

Cheers

Deepanshu

[Former Member · Accepted solution]

Hi,

Pl. find the below output for the same.

D:\Documents and Settings\p22adm>tp showbuffer p22 pf=c:\usr\sap\trans\bin\TP_DO

MAIN_P22.PFL

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

This is tp version 340.07 (release 640)

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBNAME is no longer used.

P22 buffer:

SAPKB64015 | | |will not be imported because it is t

agged.

that makes 0 transports to be imported.

tp finished with return code: 0

meaning:

Everything OK

2. The status is RDDGEN0L job is showing finished . It was executed by ddic user.

One more thing how to get the knowledge of all these things at background job level ? Is there any book or pdf ?

Pl. advice.

[Former Member · Accepted solution]

Hi Sonal,

Thanks for providing the same.

If you wish to clear you can do the following

tp r3i SAPKB64015 <SID> pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL tag=spam -Dclientcascad e=yes -Drepeatonerror=8

Will clear the Patch from OS Level.

Cheers

Deepanshu

[Former Member · Accepted solution]

Hi,

Thanks for your reply , I just want to know why the background job RDDIMPDP is terminating again and again .

If I start the job RDDIMPDP manually . The pending patch completes successfully .

Pl. advice.

[former_member603052 · Accepted solution]

Hi Sonal,

RDDIMPDP job should always be in scheduled state.Then only imports will be taken place or support packs get applied.If this job is not scheduled u need to run the Program RDDNEWPP in sa38 logging into 000 client with DDIC(This creates RDDIMPDP job scheduled).

You can also check whether it is scheduled or not from cmd prompt.

Just login with <sid>adm and type tp checkimpdp <sapsid> pf="location of your transport profile" in command line.

Regards,

Kalyan

[Former Member · Accepted solution]

Hi Sonal,

pls schedule as advice

Cheers

Deepanshu

[former_member204746 · Accepted solution]

you should have searched before asking this question. you would have found quite fast that you needed to run RDDNEWPP on all your clients on your system. this will schedule RDDIMPDP properly.

[Former Member]

hi

When the RDDIMPDP is stopped again and again ,you should have execute RDDNEWPP in SE38 or SA38 ,this will create the RDDIMPDP and it will be in scheduled state.

U can also check in OS level

{tp checkimpdp <SAPSID> pf=" :\usr\sap\trans\bin\TP_DOMAIN_SID.PFL"}

execute this in command prompt with SIDADM user.

U fill fine the state of the RDDIMPDP

Regards,

Pavan

[former_member603052]

Hi Sonal,

Is this Answered...?

Regards,

Kalyan