X

Proactive insights, news and tips from Oracle Hyperion EPM and BI Support. Learn Oracle from Oracle.

Frequently Asked Questions About EPM Cloud Data Size

Tanya Heise
Sr Principal Technical Support Engineer

Thank you to Vinay Gupta for providing information about this FAQ!

 

When it comes to EPM Cloud Data Size, have you ever asked yourself any of the following questions?

  • How much data is being used by a service instance?
  • How do I interpret the data usage report?
  • How is the data size calculated for a service instance?
  • What is the limit for data size for a service instance?

How much data is being used by a service instance?

To see how much data is being used by your EPM Cloud service instance:

  1. Click the service instance name in the MyServices portal
  2. Click on Business Metrics
  3. Select Size of Data from the drop-down menu

 

How do I interpret the data usage report?

The total size of data used by your EPM Cloud service instance is displayed in GB, in the following formats:

  • Trend in a graph format
  • Trend in a tabular format
  • Most recent value

How is the data size calculated for a service instance?

The total size of data used by your EPM Cloud service instance is the sum of the following:

  • Application data stored in Essbase
  • Artifact Snapshot created by the daily maintenance window
  • All snapshots that you have exported via EPM Automate or the Migration user interface
  • All snapshots that you have uploaded via EPM Automate or the Migration user interface
  • All data files that you have uploaded via EPM Automate or the FDMEE user interface

What is the limit for data size for a service instance?

The total size of data used by your EPM Cloud service instance cannot exceed 150 GB, per contract.

If the total size is over 150 GB, your service will keep working, but you may be notified by Oracle to reduce the data size.

 

REFERENCES:

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.