Symptom
Even though the dynamic time scheduler described in Note 923228 is
active (this is standard as of Release 7.00), the system does not
process some jobs as soon as one job finishes; instead, it does not
process these until the next regular run of the time scheduler.
Other Terms
abap/heaplimit, work process has reached abap/heaplimit'
Reason and Prerequisites
- 1. If a process is used up when the system processes the heap
memory, the system restarts the process at the end of processing, in
order to release the heap memory again. At the time of the restart, the
process is not available to the dynamic time scheduler as a target for a
new background job.
- 2. The same problem occurs if the processes start at regular intervals due to a system setting.
Solution
- 1. Set the profile parameter abap/heaplimit to a higher value. If in doubt, contact SAP Support.
- 2.
Check whether the profile parameter rdisp/wp_auto_restart is set.
Contact SAP Support to find out whether the parameter to be set at all.
Header Data
| Released On | 23.05.2011 07:13:47 | |||
| Release Status | Released for Customer | |||
| Component | BC-CCM-BTC Background Processing | |||
| Other Components |
| |||
| Priority | Recommendations / Additional Info | |||
| Category | Help for error analysis |
Validity
This document is not restricted to a software component or software component version
References
This document refers to:
SAP Notes
| 165084 | Why does my job not start? | |
| 923228 | Background job sched.: using processes that have become free | |
| 158346 | Periodic restart of work processes |
No comments:
Post a Comment