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

Shared Services & EPM Workspace

Start with 100 MB, and add more as the number of migrations with Lifecycle Management and the number of audit records increases.

Performance Management Architect

Oracle recommends starting with at least 250MB.

Administration Services

The amount of space needed depends on the metadata created; Oracle recommends starting with at least 32 MB.

Essbase Studio

The amount of space needed depends on the metadata created; Oracle recommends starting with at least 32 MB.

Reporting and AnalysisThe 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 Reporting and Analysis 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.
Planning and Calculation Manager

  • 100 MB for applications with 5,000 or fewer total members

  • 200 MB for applications with 15,000 or fewer total members

    Note:

    You can adjust the size of the system table database to match the size of the application.

Financial Management and Calculation Manager

  • 100 MB for applications with 5,000 or fewer total members

  • 200 MB for applications with 15,000 or fewer total members

    Note:

    You can adjust the size of the system table database to match the size of the application.

Performance Scorecard500 MB
Profitability and Cost ManagementOracle recommends starting with at least 250 MB.
FDMSee the Oracle Hyperion Financial Data Quality Management DBA Guide.