Oracle Database Sizing Guidelines
Oracle recommends that you set tablespaces with Auto Extend ON.
The following table describes the Oracle Database sizing guidelines.
Product | Sizing Guideline |
---|---|
Oracle Hyperion Shared Services & Oracle Hyperion Enterprise Performance Management Workspace |
Start with 100 MB, and add more as the number of migrations with Lifecycle Management and the number of audit records increases. |
Oracle Essbase Administration Services |
The amount of space needed depends on the metadata created; Oracle recommends starting with at least 32 MB. |
Oracle Hyperion Financial Reporting |
The amount of space needed depends on the aggregate size of the objects that you plan to store in the repository. Oracle recommends starting with at least 250 MB, which provides space to expand the Document Repository without having to increase the data file or tablespace. A shared pool size of 60 MB is used during configuration with EPM System Configurator. |
Oracle Hyperion Planning and Oracle Hyperion Calculation Manager |
|
Oracle Hyperion Financial Management and Calculation Manager |
|
Oracle Hyperion Financial Close Management |
See the Oracle Hyperion Financial Close Management Performance Tuning Guide, which can be found on Oracle Support by searching for document ID 1575381.1 |
Oracle Hyperion Tax Governance |
See the Oracle Hyperion Financial Close Management Performance Tuning Guide, which can be found on Oracle Support by searching for document ID 1575381.1 |
Oracle Hyperion Tax Provision |
|
Oracle Hyperion Profitability and Cost Management | Oracle recommends starting with at least 250 MB. |