How To Fix MDG_DT_UI021 - Create/Copy of Data Model not possible as the Viewcluster is locked by &2

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_DT_UI - Messages related to the Configuration Workbench UI

• Message number: 021

• Message text: Create/Copy of Data Model not possible as the Viewcluster is locked by &2

What causes this issue?

The VC_USMD001 view cluster is open in edit mode by the above mentioned
user.
As a result, all entries of the data model are locked and you cannot
create or copy a new data model.

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?

Request that the user closes VC_USMD001 or opens it in display mode
rather than in edit mode.
Continue creating the new data model from the Configuration Workbench.

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 MDG_DT_UI021 - Create/Copy of Data Model not possible as the Viewcluster is locked by &2 ?

  The SAP error message MDG_DT_UI021 indicates that the system is unable to create or copy a data model because the view cluster is locked by another user or process. This typically occurs in the context of SAP Master Data Governance (MDG) when multiple users are trying to access or modify the same data model simultaneously.
  Cause:
  
  View Cluster Locking: The view cluster associated with the data model is currently locked by another user or process. This can happen if another user is editing the same data model or if a previous session did not release the lock properly.
  Long-running Transactions: If a transaction is taking too long to complete, it may hold the lock longer than expected.
  System Issues: Occasionally, system issues or bugs can lead to locks not being released properly.
  
  Solution:
  
  
  Check for Active Sessions: Use transaction code SM12 to check for any active locks on the view cluster. You can identify the user or process that is holding the lock.
  
  If you find a lock that is no longer needed, you can delete it (if you have the necessary authorizations).
  
  
  
  Wait and Retry: If the lock is held by another user who is actively working, it may be best to wait until they finish their work and release the lock. You can communicate with the user to understand their timeline.
  
  
  Transaction Monitoring: Use transaction code SM21 to check the system log for any errors or warnings that might indicate why the lock is persisting.
  
  
  System Restart: In some cases, if the lock is due to a system issue, a restart of the relevant application server may be necessary. This should be done with caution and typically requires coordination with your Basis team.
  
  
  Contact Support: If the issue persists and you cannot identify the cause, consider reaching out to your SAP support team for further assistance. They may have tools or insights to help resolve the locking issue.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM12: To view and manage locks.
  SM21: To check system logs for errors.
  SM37: To monitor background jobs that might be causing locks.
  
  
  
  User Communication: If you are in a collaborative environment, communicate with your team members to ensure that no one else is working on the same data model at the same time.
  
  
  Documentation: Refer to SAP documentation or notes related to MDG and locking mechanisms for more detailed insights and troubleshooting steps.
  
  
  By following these steps, you should be able to resolve the locking issue and proceed with creating or copying the data model in SAP MDG.