3413225 - You don't have the resources available to publish this version or for a step when running a data action in SAP Analytics Cloud for Planning (SAC)

The data action fails with the following error:

• The results of the data action "YY" could not be published on version "XX" you don't have the resources available to publish this version. Please try later.
  OR
• The data action "YY" couldn't run on version "ZZ" because you don't have the resources available for step A ("aaaa"). Try restricting the scope of this step or try again later.

SAP Analytics Cloud (Enterprise)

This issue is not a bug, because OOM(Out of memory) issue occurs from big-size version (for example, almost 300 million as a single version). It is a consulting issue.

This issue is not a bug, because OOM(Out of memory) issue occurs from big-size version (for example, almost 300 million as a single version).

The technical support team does not have ownership of consulting, so we would like you to contact the consulting representative so that we can focus on improving product quality.

For the public tenant, we recommend optimizing the version size to less than 50 millions. And also we recommend removing redundant models.

[Operable single version size - It depend on system resources and resource usages of tenants. 50 millions is not an absolute number.]
Assuming that the model is based on about 10 columns when adding the number of dimensions and measures, there is no influence of system resources (however, public tenants are not constant because they use shared resources. Likewise, they are not constant in a concurrency environment). This is just a relative number because the version is operable at the 50 million level in the customer system.
But if the model configuration consists of 100 columns, there may be a difference of 8 to 10 times compared to the general configuration (about 10 columns). For example, assuming that a model consisting of 100 columns is up to 10 times the size of a general model, it is advisable to manage the version size at 1/10 (<5 million) or receive consulting related to system sizing. (If possible, it is recommended to define essential dimensions and measures.)

[Model/Storage division settings]
Analyzing over 50 million data from the Actual version of Sales_Archive / Determining Planning and Reporting Scope / In the case of Reporting Scope, Story can be divided into a separate model so that it can be used only for inquiry. Here, if there is a range that just needs to be stored without even needing to be viewed, you can store/restore it in Content Network Storage. Alternatively, adding a storage model may be an alternative.

For example, it can be broadly classified into three categories as shown below, and if necessary, it would be a good idea to consider model/storage division by year according to each scope.

1. Sales(Planning, Previous Year ~ )
2. Sales_Archive (for backup/Reporting): Sales_Archive_2020, Sales_Archive_2022
3. Sales_Storage (for archiving) or Content Network Storage (restore to Sales_Archive when needed): Sales_Archive_2018, Sales_Archive_2020
   
   

[Backup and Archive of the SAC planning models]
In the public tenant, all resource is shared with other tenants. So this issue (Out of memory) is required to split models "*_archive" to reduce the version size.

The customer are using a method to backup "*_archive" models with data actions. (Backups are possible via the Content Network functionality.)
If you want to maintain your current methods, such as the Blog "How to automatically backup/archive & restore your plan data", you should also keep your limits in mind and maintain them as the bottom of the blog.
The "*_archive" models are currently backuped without partitioning, increasing their size. It is determined that OOM has occurred as it exceeds the amount of resources currently occupied and available in the Commons system.
Therefore, we recommend that you split and backup "_archive" models. For example, configure split "_archive" models by backing up the model by splitting the size of the "Actual" version into historical data.
Once the partitioning is complete, delete the partitioned data in the "*_archive" models to maintain the appropriate version size.

Most of OOM messages are not a bug and requires optimizing the size of a specific public version of the SAC model.

Blog "How to automatically backup/archive & restore your plan data": https://community.sap.com/t5/technology-blogs-by-members/how-to-automatically-backup-archive-restore-your-plan-data/ba-p/13475189

[Continuous memory management]
Memory management in public systems is something that administrators pay attention to and continuously monitor 
on a daily basis (check the private version in the Active state and revert/delete/publish) 
, weekly (check the version size of the planning model and back it up, generally using less than 50 millions recommended) 
and Monthly (Archive model confirmation and maintenance - archiving/management with Content Network Storage), etc. are examples.

Due to the nature of the public system, continuous memory management is required because it is closely related to the use of common resources with other tenant users.

Therefore please try to reduce the high data processing in your scenarios to reduce the high memory usage in HANA.
Please note, you can use the reporting for the performance of BI queries, of data actions and also for the statistics of private versions that is available in SAC to identify the scenarios that are expensive and can reduce the overall performance of the system: 

• https://blogs.sap.com/2021/04/13/sap-analytics-cloud-data-action-performance-statistics-and-analysis/
• https://blogs.sap.com/2020/09/24/performance-statistics-and-analysis/
• https://blogs.sap.com/2022/10/14/sap-analytics-cloud-private-versions-statistics-and-analysis/

• SAP Analytics Cloud Planning : do you encounter performances issues? What can you do before contacting SAP?
• SAP Community  https://www.sap.com/community.html

SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Sac, Acquisition, Model, Connect, Story, Tenant, Import, Failed, Using, Working, SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Connection, Sac, Connector, Live, Acquisition, Up, Set, setup, Model, BW, Connect, Story, Tenant, Import, Failed, Using, Working, SAML, SSO, sapanalyticscloud, sap analytical cloud, sap analytical cloud, SAC, sap analyst cloud, connected, failure, stopped, sap analyst cloud, https://hcs.cloud.sap, https://hanacloudservices.cloud.sap, https://cloudanalytics.accounts.ondemand.com, https://hanacloudservices-us.accounts.ondemand.com, https://www.sap.com, https://help.sap.com, predictive analytics (analysis), data analysis (analytics) tools, analytics tools, sap analytics cloud, data literacy, advanced analytics, data democratization, analytics software, real time analytics, self service analytics, advanced data analytics, analytics as a service, analytics cloud / cloud analytics, saas analytics, cloud bi, enterprise planning, cloud data analytics, cloud based analytics, analytics cloud platform, modern analytics, real time analysis, cloud analytics solution(s), what is sap analytics cloud, cloud analytics tools, analytics in the cloud, cloud analytics software, dashboard, limited resource , KBA , LOD-ANA-PL-DA , Data Actions , LOD-ANA-PL-AF , Advanced Formulas , LOD-ANA-PL-VER , Version Management , How To