Background jobs stacking up - SM37

[ThomasKjelsrud]

Hi all,

I have a problem with the background jobs. There are lots and lots of jobs of type ARFC that are just staying in released status, and not moving into ready. This is affecting other jobs that are experiencing very long delay times and jobs get canceled because the latest start time is exceeded.

I have tested that the instance is correctly configured for background processing, and is running with 6 btc jobs. I am on a R/3 4.7 SR1 200 server.

Does anyone have some hints for me on how to solve this situation?

Regards,

Thomas

[Former Member · Accepted solution]

Hi Thomas,

Background jobs are stored in the table called TBTCS & it can viewed from the T code SE11 & check whether RDD* jobs are triggering properly, user SE38 and run the jobs manually.

Cheers,

Shyam.

[Former Member]

Hi Thomas,

As per SAP Note 90428:

-

---

4. If a large number of ARFC* jobs are available in the system, this

can be connected to the fact that destinations are not maintained

correctly. Check this in the SM58/SM59 (test the connections).

-

---

All the ARFC* jobs are pending to be started, which can lead all other time controlled jobs to be delayed.

General information:

The ARFC jobs have time-based start criteria so they only run at every

interval of the time-based job scheduler. Because the jobs have a very short run time, probably just

one or two seconds, this makes it appear as if the background processes

are idle all the time. If you check the queue of released ARFC jobs

in SM37, you are likely to see that the jobs do get executed gradually,

but probably new ARFC jobs were added all the time.

You can find the problem that causes the ARFC jobs to be created in

SM58. Once the affected RFC destinations work correctly, the jobs

should start being processed. Optionally you can switch off the scheduling

of an ARFC jobs for failed calls via SM59 > Destination > TRFC options

> Suppress background job if connection error. Press the F1 help on

this field for instructions on how to resubmit failed TRFC calls

if no job is created.

Other related notes:

#366807 Significance of background jobs ARFC:*

#372094 Many background jobs ARFC:SYSLOAD1<client><user>

I hope this information helps clear the issue.

Regards, Mark

[Former Member]

Hi Thomas,

jobs which are stuck at ARFC mode needs to trigger other event controlled jobs. since they are updating the Database, unless those jobs trigger this job cannot run forward so try to find what kind of jobs from the user who scheduled the job and then take the action if the jobs are related to support packages and releasing of change request then try to schedule RDD* jobs under user DDIC in 000 client

this is not due to instance consistency

Samrat