1. Administrator's Guide
  2. Optimizing Performance
  3. Tuning Financial Management Applications
  4. Basic Design Considerations

Basic Design Considerations

  • If Data Audit feature is not part of business requirements, then it is recommended to turn off data auditing. Degradation in performance has been observed for applications with a Data Audit table more than 10GB.

    Tip:

    To turn off auditing of members, change the EnableDataAudit attribute to N for all members in your metadata file.

  • Rules must always be tested prior to loading in a production environment to avoid any pitfalls of poorly designed rules (for example, data explosion from rules). Efficient rules are critical for acceptable system performance.

  • Oracle Hyperion Financial Management does all processing through subcubes while they are stored in RAM, so the larger the subcube, the larger the impact on performance. Try to minimize subcube size as much as possible, for example, no subcube should exceed the 200,000 base record limits in order to ensure optimal system performance.

  • Loading to or calculating zeros in a Financial Management application is not recommended. Zeros are stored as data, which increases the database size and can affect performance. It is recommended that only numeric information, such as 1000, be stored in Financial Management. See the Data File section in the Oracle Hyperion Financial Management User's Guide .

  • If Financial Management is not properly shut down, temporary files may remain upon reboot. To ensure optimal performance, it is recommended that you delete all *.db.* file names from the Financial Management Server Working folder before launching Financial Management.

  • For attaching multiple documents to a data grid or process unit, Oracle recommends that you attach no more than three documents to a cell. Each document should be smaller than 100K to limit the performance effect on the database.

    Tip:

    You can set a size limit for document attachments and a maximum number of document attachments by user when you create an application. You can set the limits in the AppSettings attribute for the application metadata.

  • Use the Consolidate All option only under appropriate circumstances. If this option is used, the system does not skip entities with NoData, which can have a significant impact on consolidation performance.

    Tip:

    The Consolidate (Impacted Consolidation) is the most efficient option, because only entities that require logic or consolidation are updated by the system. The Consolidate All with Data option is useful for updating system status from OK SC to OK after metadata changes. For additional information, see the Consolidation Options section of the Oracle Hyperion Financial Management User's Guide .