In Essbase Administration Services (EAS) go to the Database Properties and select the Storage Tab.
To add a new volume or to change values for a previously allocated volume:
1. In the Disk Volume text box, enter the volume name or select a previously allocated volume.
Note that you can only add volumes that are internal discs – shared Network drives do NOT show up as an option and it is not recommended to use shared network drives to store the data of an Essbase Database
2. Specify Partition Size.
– Partition Size represents the maximum space that Hyperion Essbase uses on the volume. The default value is Unlimited; the minimum is 8,192 kilobytes.
3. Specify File Type.
– You can specify index files, data files, or both. The default is Index + Data.
4. Specify File Size.
-File Size represents the maximum size that a file specified in File Type can attain before Hyperion Essbase creates a new file. The default value is 2 GB (2097152 kilobytes); the minimum value is 8,192 kilobytes.
5. Click Set.
6. Stop and restart the database.
If the database is already loaded with data then .pag and .ind files already exist. These files will stay within the \Essbase\app\appname\dbname directory. The above process will only span “new” .pag and .ind files. If the intention is to have ALL .pag and .ind moved then the following will need to be done after the above spanning values are set:
1. Export the data.
2. Clear the database.
3. Stop and restart the database.
4. Reload the data.
5. Recalculate the database.
Forcing a restructure should also move the existing .pag and .ind files to the new location.
In terms of Business Rules and Calc Scripts – these are both ran by Essbase. Essbase can be tuned to take advantage of dual and / or quad core processors.
- Up to version 184.108.40.206 Essbase can use a maximum of 4 (integer between 1-4) CPU per Essbase application on 32 bit platforms when running calc parallel on a Block Storage application.
For Block Storage on 64-bit platforms, an integer between 1-8.
The default value, 1, specifies serial calculation: no parallel calculation takes place.
- From Version 220.127.116.11 on the limits have increased to:
BSO: up to 64 threads for 32 bit Installations and 128 threads for 64-bit Installations.
ASO: up to 128 threads for 32-bit OR 64-bit installs.
- Essbase (<= v 18.104.22.168.x) can use a maximum of 8 (integer from 1-8, default value 2) CPU per Essbase application when running calc parallel on an Aggregate Storage application (ASO).
- Essbase can use any number of CPU available when running queries.
Each running query however can only use one CPU.
- Essbase relies on the machine to actually assign the threads to different CPUs.
- Adding more CPUs to a machine should never hurt performance.
At the very least it should increase query concurrency on the machine as long as disk I/O doesn’t become a bottle neck.
- When more than 4 or 8 CPUs are available (depending on whether you are using ASO or BSO) Essbase can use these CPUs to make concurrent calculations on different applications faster as long as disk I/O doesn’t become a bottle neck.
Yesterday I received one of those phone a friend calls regarding a rumor about “EPMA won’t be part of 22.214.171.124”
This must be a hot-button topic since I received a crazy fast response from my Oracle contacts.
Interestingly EPMA got a bad rep (rightly so) due to some pretty bad issues in earlier releases. As of 126.96.36.199 and later it is quite mature and stable.
So the rumor is a bit of a trick statement since:
- Oracle has stated Enterprise Performance Management Architect (EPMA) is not the strategic direction.
- Oracle has stated EPMA is not being actively enhanced.
- Oracle has publicly stated the next “Hyperion” release is EPM 12 not 188.8.131.52 — now things could change however 184.108.40.206 is not on a release map at this time.
- My contacts who are very well placed state EPMA will be part of EPM 12
So what does this mean?
- You don’t need hurry and remove EPMA from your environment in prep for future upgrades.
- I would not suggest putting effort into EPMA data integrations; definitely look at FDMEE or other techniques.
- EPMA will still require IIS and Windows — EPMA is not being ported from an ASP.NET solution to Java; therefore won’t be part of Oracle’s EPM Cloud nor a core part of Exalytics deployments.
We believe the forth coming Dimension Management Cloud Services Solution is something to look at closely for future needs.
If you do decide to use EPMA make sure you have thought about the other potential solutions and have a good rationalization for this tool.
Think hard about your use cases for future deployments; if you are headed to the clouds like many realize there will be no EPMA.
Although EPMA is not the strategic direction it does offer some capabilities such as being able to rename members in HFM which are not accomplished in other avenues.