How To Fix RSENQ068 - InfoCube &1 locked by terminated time-change run &2

SAP Error Message - Details

• Message type: E = Error

• Message class: RSENQ - Lock Manager

• Message number: 068

• Message text: InfoCube &1 locked by terminated time-change run &2

What causes this issue?

Time-change run with number &V2& has been terminated. This change run
modifies the key date of time-dependent hierarchies. It also modified
aggregates of InfoCube &V1&.
The time-change run was started on &V3& by user &V4&.

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?

Restart the time-change run.

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 RSENQ068 - InfoCube &1 locked by terminated time-change run &2 ?

  The SAP error message RSENQ068 indicates that an InfoCube is locked due to a terminated time-change run. This typically occurs when a process that updates or changes data in the InfoCube is interrupted or fails, leaving the InfoCube in a locked state. Here’s a breakdown of the cause, solution, and related information for this error:
  Cause:
  
  Terminated Time-Change Run: The most common cause is that a time-change run (which is part of the data loading or updating process) was terminated unexpectedly. This could be due to various reasons such as system crashes, resource issues, or manual termination.
  Locking Mechanism: SAP uses a locking mechanism to prevent data inconsistencies during updates. If a process is terminated, the lock may not be released properly, leading to this error.
  
  Solution:
  
  Identify the Lock: Use transaction code SM12 to check for locks on the InfoCube. You can filter by the user or the object type to find the specific lock related to the terminated time-change run.
  Release the Lock: If you find a lock that is no longer valid (e.g., from a terminated process), you can manually delete the lock entry in SM12. Be cautious when doing this, as it may affect ongoing processes.
  Check for Background Jobs: If the time-change run was part of a background job, check the job logs in transaction SM37 to understand why it failed. This can help prevent future occurrences.
  Restart the Time-Change Run: After releasing the lock, you may need to restart the time-change run to ensure that the InfoCube is updated correctly.
  Monitor System Resources: If the issue is recurring, monitor system resources (CPU, memory, etc.) to ensure that the system is not under heavy load, which could lead to process terminations.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage locks.
  SM37: To check background job logs.
  RSA1: To access the Data Warehousing Workbench for InfoCubes.
  
  
  Documentation: Refer to SAP Help documentation for more details on InfoCubes and data loading processes.
  Support: If the issue persists, consider reaching out to SAP support for further assistance, especially if it involves complex data models or configurations.
  
  By following these steps, you should be able to resolve the RSENQ068 error and restore normal operations for the affected InfoCube.