24.01.2011 Page 1 of 2

SAP Note 26966 - Background jobs do not start whentransporting

Note Language: English Version: 7 Validity: Valid Since 20.11.2003

Summary

SymptomTransports which were started with the transport control program tp do notexit. In the tp log file SLOG, the following messages are periodicallywritten:Background job not running properly. Function: ... Jobcount: ... Status: SPlease check the system. Use Transactions SM21, SM37, SM50.

Other termsRDDIMPDP, RDDMASGL, RDDDIS0L, RDDGEN0L, RDDDIC0L, RDDDIC1L, RDDDIC3L,RDDVERSE, RDDVERSL, RDDEXECLTR496

Reason and PrerequisitesWhen executing transports, programs are started within the SAP System.These programs are scheduled as background jobs.

o Background jobs are started as separate processes (type BTC inTransaction SM50). If all such background job process slots areoccupied no new background jobs can be started. These jobs staylocked until there are process slots free.

o Sporadically it may also happen that the scheduled batch jobs hangin status "ready" or "scheduled" despite of there being free BTCprocesses. So far we have no plausible explanation to thatphenomenon.

SolutionThe solution to this depends on whether the background processes are justtemporarily over-used, or whether a long-term bottleneck exists.If the capacity overload is only caused by one or two very lengthybackground jobs that are not regularly scheduled, a little patience is thebest remedy. After these jobs terminate, the transport programs will alsoexit correctly.The number of background processes or application servers which are used toprocess background jobs should be increased if the capacity overload forbackground processing is long-term. Details for this can be found in the"BC System Administration" manual, in chapter 4 (Configure BackgroundProcessing).The Transactions SM50 (process overview of an application server), SM51(overview of the application servers) and SM37 (overview of backgroundjobs) can be used for analysis. Details for this can also be found in the"BC System Administration" manual in chapter 4.

o If the batch jobs do not start despite of free BTC processes, youcan work around the problem by scheduling those "hanging" jobsagain using Transaction SM37 (Job -> Repeat scheduling ->Immediate). It is important that you repeat the job scheduling asuser DDIC (the user under which the original job had beenscheduled).According to our experience, the batch system will work withoutproblems afterwards.

24.01.2011 Page 2 of 2

SAP Note 26966 - Background jobs do not start whentransporting

Header Data

Release Status: Released for CustomerReleased on: 21.11.2003 16:09:13Master Language: GermanPriority: Recommendations/additional infoCategory: PerformancePrimary Component: BC-CTS Change and Transport System

The Note is release-independent

Related Notes

Number Short Text

556941 Transport FAQ: Error scenarios

556734 FAQ Transport: Setup and further information

71353 Transports hang during background steps

50104 Job class of background jobs during the import