Do you have any question about this error?
Message type: E = Error
Message class: RSM1 - Messages for AWB, Scheduler and Monitor (new)
Message number: 035
Message text: The last delta load is still running; no new request possible
The last delta load is still running; no new requests possible.
A repeat request is currently running for this DataSource.
You can only request a new delta once this loading process is
completed.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check the status of this delta request in the Monitor.
If the load has been terminated for some reason, remove the error;
Set the request to red or green using QM action, so that the next delta
or repeat can be requested.
Error message extract from SAP system. Copyright SAP SE.
RSM1035
- The last delta load is still running; no new request possible ?The SAP error message RSM1035, "The last delta load is still running; no new request possible," typically occurs in the context of SAP BW (Business Warehouse) when a delta load process is still active, preventing new delta requests from being processed. This can happen in scenarios where data is being extracted from a source system, and the delta extraction process has not yet completed.
Cause:
- Ongoing Delta Load: The most common cause is that a previous delta load is still in progress. This can happen if the delta extraction process takes longer than expected due to large volumes of data or performance issues.
- Locking Mechanism: SAP BW uses a locking mechanism to ensure data consistency. If a delta load is running, it locks the process to prevent other delta loads from starting.
- Long Running Queries: Sometimes, long-running queries or data loads can cause delays in the delta process.
- System Performance Issues: Performance issues in the source system or the BW system can lead to delays in the delta load process.
Solution:
- Check Delta Load Status: Use transaction codes like
RSA1
(Data Warehousing Workbench) orRSMO
(Monitor Delta Queue) to check the status of the delta load. If it is still running, you may need to wait for it to complete.- Monitor Process Chains: If the delta load is part of a process chain, check the process chain status in transaction
RSPC
. If the process is stuck, you may need to analyze and resolve any issues.- Terminate Long-Running Processes: If you determine that the delta load is stuck or taking too long, you may need to terminate the process. This can be done using transaction
SM37
(Job Monitoring) to find and cancel the job.- Check for Locks: Use transaction
SM12
to check for any locks that might be preventing the delta load from completing. If you find any unnecessary locks, you can delete them.- Increase Performance: If delta loads frequently take too long, consider optimizing the extraction process, such as adjusting the data volume, improving performance on the source system, or scheduling loads during off-peak hours.
- Re-run Delta Load: After resolving the issue, you can re-initiate the delta load process.
Related Information:
RSA1
: Data Warehousing WorkbenchRSMO
: Monitor Delta QueueRSPC
: Process Chain MonitoringSM37
: Job MonitoringSM12
: Lock Entry ListBy following these steps, you should be able to resolve the RSM1035 error and successfully manage your delta load processes in SAP BW.
Get instant SAP help. Start your 7-day free trial now.
RSM1034
The last repeat load is still running; no new request possible
What causes this issue? The last repeat load is still running; no new requests are possilbe. A repeat request is currently running for this DataSourc...
RSM1033
Object & saved to order &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSM1036
Selection conditions replaced by last init. selection conditions
What causes this issue? Selection conditions replaced by init. selection conditions. No new selections can be made when requesting delta data from a ...
RSM1037
No active transfer rules for source system &2 InfoSource &1
What causes this issue? No active transfer rule for source system &V2&, InfoSource &V1&. There are no active transfer structures for ...
Click on this link to search all SAP messages.