How To Fix RSENQ058 - InfoCube &1 is locked by change run &2

SAP Error Message - Details

• Message type: E = Error

• Message class: RSENQ - Lock Manager

• Message number: 058

• Message text: InfoCube &1 is locked by change run &2

What causes this issue?

Change run with number &V2& is running currently. It was started on &V3&
by user &V4&.
The change run also modified aggregates of InfoCube &V1&.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Wait until the change run has finished.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSENQ058 - InfoCube &1 is locked by change run &2 ?

  The SAP error message RSENQ058 indicates that an InfoCube is currently locked by a change run. This typically occurs when a data load or a process that modifies the InfoCube is in progress, preventing other processes from accessing or modifying the data in that InfoCube.
  Cause:
  
  Ongoing Change Run: The most common cause is that a data load or change run is currently being executed on the InfoCube, which locks it to ensure data integrity.
  Long-Running Processes: If a data load takes longer than expected, it can lead to prolonged locking of the InfoCube.
  Failed Processes: Sometimes, if a previous data load or process failed, it might leave the InfoCube in a locked state.
  
  Solution:
  
  Wait for Completion: The simplest solution is to wait for the ongoing change run to complete. You can monitor the status of the data load in the Data Warehousing Workbench or the relevant transaction codes (like RSA1).
  Check for Active Processes: Use transaction code SM37 to check for any active jobs related to the InfoCube. If you find a job that is stuck or taking too long, you may need to investigate further.
  Terminate the Job: If you determine that the job is not progressing and is causing the lock, you can terminate it. Be cautious with this approach, as it may lead to data inconsistencies. You can do this from SM37 by selecting the job and choosing to cancel it.
  Check for Locks: Use transaction code SM12 to check for any locks on the InfoCube. If you find locks that are not being released, you may need to delete them, but ensure that you understand the implications of doing so.
  Re-run the Process: After resolving the lock, you may need to re-run the data load or change run that was initially blocked.
  
  Related Information:
  
  Transaction Codes:
  
  RSA1: Data Warehousing Workbench
  SM37: Job Monitoring
  SM12: Lock Entries
  
  
  Monitoring Tools: Use the SAP BW monitoring tools to keep track of data loads and change runs to prevent future occurrences of this issue.
  Best Practices: Schedule data loads during off-peak hours to minimize the impact of locks on other processes. Regularly monitor and optimize data load processes to ensure they complete in a timely manner.
  
  If the issue persists or if you are unsure about terminating jobs or deleting locks, it is advisable to consult with your SAP Basis or BW team for further assistance.