How To Fix DMCLG336 - Access plan calculation still running in sender system

SAP Error Message - Details

• Message type: E = Error

• Message class: DMCLG - DMC Tool Development

• Message number: 336

• Message text: Access plan calculation still running in sender system

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 DMCLG336 - Access plan calculation still running in sender system ?

  The SAP error message DMCLG336, which states "Access plan calculation still running in sender system," typically occurs in the context of data transfer processes, particularly when using SAP Data Services or SAP Landscape Transformation (SLT) for data replication. This error indicates that the system is still processing the access plan for the data transfer, and it cannot proceed until that calculation is complete.
  Cause:
  
  Long-running Access Plan Calculation: The access plan calculation may take longer than expected due to a large volume of data, complex queries, or system performance issues.
  System Load: High system load or resource contention can delay the completion of the access plan calculation.
  Locks: There may be locks on the database that prevent the access plan from being calculated.
  Configuration Issues: Incorrect configuration settings in the data transfer process can lead to inefficiencies in access plan calculation.
  
  Solution:
  
  Wait for Completion: Often, the simplest solution is to wait for the access plan calculation to complete. Monitor the system to see if the process finishes.
  Check System Performance: Use transaction codes like ST03N or ST04 to analyze system performance and identify any bottlenecks.
  Review Locks: Use transaction code SM12 to check for any locks that might be affecting the access plan calculation. If locks are found, investigate and resolve them.
  Optimize Queries: If the access plan calculation is taking too long due to complex queries, consider optimizing the queries involved in the data transfer.
  Adjust Configuration: Review the configuration settings for the data transfer process to ensure they are optimized for performance.
  Increase Resources: If the system is under heavy load, consider increasing system resources (CPU, memory) or scheduling data transfers during off-peak hours.
  Check Logs: Review relevant logs (e.g., SLT logs, Data Services logs) for any additional error messages or warnings that could provide more context.
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to DMCLG336 for any specific patches or updates that may address this issue.
  Documentation: Review SAP documentation on data replication and access plan calculations for best practices and optimization techniques.
  Community Forums: Engage with SAP community forums or support channels for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to involve SAP support for further investigation.