How To Fix MDC_HDB_MTC058 - Status check in progress; wait until status check is completed

SAP Error Message - Details

• Message type: E = Error

• Message class: MDC_HDB_MTC - Message class for master data consolidation matching

• Message number: 058

• Message text: Status check in progress; wait until status check is completed

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message MDC_HDB_MTC058 - Status check in progress; wait until status check is completed ?

  The SAP error message MDC_HDB_MTC058 with the description "Status check in progress; wait until status check is completed" typically occurs in the context of SAP HANA database operations, particularly when using the Multi-Database Container (MDC) feature. This message indicates that a status check is currently being performed on a database or system, and the operation you are trying to execute cannot proceed until the status check is completed.
  Cause:
  
  Ongoing Status Check: The most common cause of this error is that a status check is already in progress for the database or system. This could be due to a previous operation that initiated a status check, such as a system restart, database upgrade, or maintenance task.
  Long-running Operations: If there are long-running operations or maintenance tasks, they may trigger a status check that takes time to complete.
  Concurrency Issues: Multiple users or processes trying to perform operations on the same database can lead to conflicts, causing one operation to wait for another to complete.
  
  Solution:
  
  Wait for Completion: The simplest solution is to wait for the ongoing status check to complete. You can monitor the status of the operation through the SAP HANA Studio or other monitoring tools.
  Check System Logs: Review the system logs or monitoring tools to identify what operation is causing the status check to take longer than expected. This can provide insights into whether there are any issues that need to be addressed.
  Retry the Operation: Once you have confirmed that the status check has completed, you can retry the operation that triggered the error.
  System Restart: If the status check seems to be stuck and does not complete after a reasonable amount of time, you may need to consider restarting the SAP HANA database. However, this should be done with caution and ideally during a maintenance window, as it can impact users and processes.
  Consult Documentation: Refer to the official SAP documentation or support notes related to your specific version of SAP HANA for any known issues or additional troubleshooting steps.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific issues related to your version of SAP HANA that might provide additional context or solutions.
  Monitoring Tools: Utilize SAP HANA Studio, SAP HANA Cockpit, or other monitoring tools to keep track of database operations and their statuses.
  Performance Tuning: If status checks are frequently taking a long time, consider reviewing your system's performance and configuration to identify potential bottlenecks.
  
  If the issue persists after trying the above solutions, it may be beneficial to reach out to SAP Support for further assistance.