How To Fix CM_SUB_INFOSYS028 - The query was terminated

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_SUB_INFOSYS - Substance information system

• Message number: 028

• Message text: The query was terminated

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 CM_SUB_INFOSYS028 - The query was terminated ?

  The SAP error message CM_SUB_INFOSYS028, which states "The query was terminated," typically occurs in the context of SAP BW (Business Warehouse) or SAP HANA when a query execution is interrupted or fails to complete successfully. Here are some common causes, potential solutions, and related information for this error:
  Causes:
  
  Timeout Issues: The query may take too long to execute, leading to a timeout. This can happen if the query is complex or if the underlying data volume is large.
  Resource Limitations: Insufficient system resources (CPU, memory, etc.) can cause the query to be terminated.
  Database Locks: If there are locks on the database tables that the query is trying to access, it may lead to termination.
  Network Issues: Connectivity problems between the SAP application server and the database can also cause queries to be terminated.
  Query Design: Inefficient query design or poorly optimized queries can lead to performance issues and subsequent termination.
  User Interruptions: The user may have manually terminated the query execution.
  
  Solutions:
  
  Increase Timeout Settings: If the query is timing out, consider increasing the timeout settings in the SAP BW or HANA system.
  Optimize the Query: Review the query design for optimization opportunities. This may include reducing the amount of data being processed, using aggregates, or simplifying calculations.
  Check System Resources: Monitor system performance and resource usage. If necessary, allocate more resources or schedule heavy queries during off-peak hours.
  Database Locks: Investigate any locks on the database that may be affecting the query. You can use transaction codes like SM12 to check for locks.
  Network Stability: Ensure that the network connection between the application server and the database is stable and reliable.
  Review Query Execution Plan: Analyze the execution plan of the query to identify bottlenecks or areas for improvement.
  User Training: If users are manually terminating queries, provide training on how to run queries efficiently and the implications of terminating them.
  
  Related Information:
  
  Transaction Codes: Use transaction codes like ST22 (Dump Analysis), SM37 (Job Monitoring), and ST03N (Workload Analysis) to gather more information about the error and system performance.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Performance Tuning: Consider engaging in performance tuning activities for your BW or HANA system to improve overall query performance.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.