How To Fix PU860 - ST05_GET_SUMMARY_TABLES ended with an error

SAP Error Message - Details

• Message type: E = Error

• Message class: PU - Upgrade and Transport Log Messages

• Message number: 860

• Message text: ST05_GET_SUMMARY_TABLES ended with an error

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 PU860 - ST05_GET_SUMMARY_TABLES ended with an error ?

  The SAP error message "PU860 ST05_GET_SUMMARY_TABLES ended with an error" typically relates to issues encountered during the execution of the ST05 transaction, which is used for performance tracing in SAP. This error can occur for various reasons, and here are some common causes, potential solutions, and related information:
  Causes:
  
  Database Issues: There may be problems with the underlying database, such as connectivity issues, locks, or corruption.
  Insufficient Authorizations: The user executing the transaction may not have the necessary authorizations to access certain tables or perform specific actions.
  System Configuration: Misconfigurations in the SAP system or the tracing settings can lead to errors.
  Memory Issues: Insufficient memory or resources allocated to the SAP instance can cause the process to fail.
  Software Bugs: There may be bugs in the SAP version you are using that affect the ST05 transaction.
  
  Solutions:
  
  Check Database Connectivity: Ensure that the database is up and running, and there are no connectivity issues. You can check the database logs for any errors.
  Review Authorizations: Verify that the user has the necessary authorizations to execute the ST05 transaction and access the required tables.
  Adjust Configuration: Review the configuration settings for ST05 and ensure they are set correctly. You may need to consult with your SAP Basis team for assistance.
  Monitor System Resources: Check the system's memory and resource usage. If the system is low on resources, consider increasing the allocated memory or optimizing the workload.
  Update SAP: If you suspect a bug, check for any available patches or updates for your SAP system that may address the issue.
  Check ST05 Settings: Sometimes, resetting the ST05 settings or clearing previous traces can resolve issues. You can do this by stopping the trace and then restarting it.
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error. SAP Notes often contain fixes or workarounds for known issues.
  Transaction Codes: Familiarize yourself with related transaction codes such as ST22 (Dump Analysis) and SM21 (System Log) to gather more information about the error.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.