Solution : https://service.sap.com/sap/support/notes/26966 (SAP Service marketplace login required)
Summary :
When executing SAP transports with the tp control program, issues may arise where transports do not exit as expected. In such situations, the tp SLOG file frequently logs messages about non-functioning background jobs. These issues typically stem from all available background processes (BTC type) being occupied, preventing new jobs from initiating. Alternatively, background jobs might remain in a 'ready' or 'scheduled' status even with available BTC processes, a phenomenon currently without a clear explanation. To resolve these issues, patience may suffice for one-time overloads, while persistent issues require increasing background process or application server capacity as outlined in the "BC System Administration" guide, chapter 4. If jobs do not start despite free process slots, rescheduling them with Transaction SM37, especially as user DDIC, often rectifies the issue according to SAP's experience. Important transactions for troubleshooting include SM21, SM37, and SM50.
Key words :
tp log file slog, long-term bottleneck exists, transport control program tp, scheduled batch jobs hang, background job process slots, process slots free, jobs stay locked, bc system administration, free btc processes, lengthy background jobs
Related Notes :
| 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 |