topic Re: Archiving Delete job failed in Application Development and Automation Discussions

Archiving Delete job failed

Former Member — Thu, 31 Oct 2013 17:21:25 GMT

Hello,

We are using standard delete archiving program RSARCHD, to delete the data for archiving object CO_ITEM.

Recently we have encountered a issue in the delete job. In job log of that program is saying :

We have checked the Variant and authorization and everything is fine. Can anybody able to tell me what is the issue?

For other programs it is working fine but we have encountered this error message 2-3 times in the past also.

Re: Archiving Delete job failed

Former Member — Thu, 31 Oct 2013 18:03:29 GMT

Check error massage in SM21 and ST22.

Re: Archiving Delete job failed

Former Member — Fri, 01 Nov 2013 01:53:21 GMT

Hello Shamik,

As suggested by Pramod you have to analyze the dump in ST22 and check whether you are getting any clue from there. Other option is to debug the program RSARCHD with the same variant you provided for the background job.

I believe you are scheduling the delete job through the transaction SARA, please confirm.

Let me know if you still have difficulties.

Thanks

Nivash S

Re: Archiving Delete job failed

Former Member — Fri, 01 Nov 2013 09:09:17 GMT

Thanks for the reply. I have checked ST22 and SM21 , but there is no error message or dump.

I have tried to debug the RSARCHD program with the same variant ( only change the mode from Production to TEST) and found that lots of other CO_ITEM Delete jobs are in queue which was run previously but cancelled somehow.

How to delete the incorrect old delete jobs from SARA?

If any Write or Delete jobs are failed then how to remove those jobs and other details ?

Re: Archiving Delete job failed

Former Member — Sun, 03 Nov 2013 22:56:45 GMT

Hello Shamik,

If you feel that the incorrect delete jobs (those ran previously) are creating problem, and by clearing those you can resolve the issue then here you go. ADMI_RUN is the table where all the job references are stored. by passing the Archiving object and the run number you can get those records. I dont see any table maintenance for this table, so probable to delete these you have to get the firefighter access in production.

but if you ask me this should not be the root cause, but still you can give a try. All the best.

Thanks

Nivash S