3545396 - SAC Story execution takes too long or Analytic Model returns the error: booked memory limit reached

• SAC Story execution takes too long and it effects to overall system performance.
• SAC Story execution finishes with the following error message:
  Destination host is unreachable
• Analytic Model execution in Datasphere returns the following error message: The query executed with errors. Caught exception : exception 70000004: cannot allocate enough memory: Allocation failed; Reason: booked memory limit reached

• SAP Datasphere 2024.24 and beyond
• SAP Analytics Cloud 2024.24 and beyond

Based on the current model, the available booked capacity of the database is overloaded, especially regarding the number of occupied CPU threads. This leads to slowdowns for all other related activities on the tenant. 

In order to analyze and find the root cause of this issue, the following needs to be checked:

• The overall utilization of the system. See Help Portal documentation for system monitoring. 
• Turn on the Expensive Statement Tracing and query the model/view by writing such a SQL Statement to find out memory and CPU per seconds used:

        SELECT COUNT(*) from "Schema"."ModelName or ViewName";

• The CPU utilization of the database goes up significantly, accompanied by an increase in consumed memory; the model needs to be optimized.

 

See the blog Performance analysis in the SAP Datasphere

story performance, tenant slow, analytic model slow, booked memory limit reached , KBA , DS-MD-AM , Analytic Model , LOD-ANA-DES , Story Design & Visualizations , DS-MD , Modeling (Data Builder) , DS-MD-VIW , Views , Problem

SAP Analytics Cloud all versions ; SAP Datasphere all versions