Frequently Asked Questions
Which Operating Systems are supported?
See the Oracle Enterprise Performance Management System Supported Platform Matrix: Oracle EPM Supported Platform Matrix.
Must the relational database be 64-bit?
The database can be either 32-bit or 64-bit, as long as it is a supported DBMS type and version.
Considerations must be made for third-party and extending software. By default, the Oracle Hyperion Financial Management installation only installs 64-bit software on a 64-bit operating system. This means that only the 64-bit client components are installed on the Financial Management application server. When 32-bit connectivity is required, components may not function unless the 32-bit client software is installed on the 64-bit application server. For more information, refer to the Oracle Enterprise Performance Management System Installation and Configuration Guide.
What are the memory limitations of 64-bit Financial Management?
In practical terms, 64-bit Financial Management is limited by physical memory, rather than virtual memory. It can take advantage of all available physical memory after the proper memory parameter adjustments are made.
Are there any memory settings that must be tuned for Financial Management?
Financial Management default memory settings are appropriate for a small to medium size application in a 32-bit environment. To take full advantage of available memory, Oracle recommends the following settings for a monthly application. The relevant settings are MaxNumDataRecordsInRAM and MaxDataCacheSizeinMB, which should be changed. The following table contains suggested values for these parameters depending on available memory. The table assumes that Financial Management is the only memory-intensive process running on the machine and running only one Financial Management application. If multiple applications are active, then divide the Total physical Memory installed on the server by the number of Financial Management applications, to determine the Available Physical Memory for each application.
| Available Physical Memory | MaxNumDataRecordsinRAM | MaxDataCacheSizeinMB |
|---|---|---|
| 4 | 4,000,000 | 500 |
| 8 | 10,000,000 | 1500 |
| 16 | 30,000,000 | 4500 |
| 32 | 60,000,000 | 9000 |
Example: On a server with 24 GB of RAM with 2 active monthly Financial Management applications, the MaxNumDataRecordsInRAM value should be 22,500,000 and the MaxDataCacheSizeinMB value should be 3375.
On average, the amount of memory used for one data record in a monthly application is 112 bytes, a weekly application uses 472 bytes per data records and a daily application uses 3,296 bytes per data record.
For a Weekly application, divide the MaxNumDataRecordsInRAM by 4, without changing the value in the last column for MaxDataCacheSizeinMB.
For Daily applications, divide the MaxNumDataRecordsInRAM by 30, without changing the value in the last column for MaxDataCacheSizeinMB.