Database Reference
In-Depth Information
specifically can be very complex and may have upwards of 50 servers using one physi-
cal frame. use of disk benchmarking tools can assist troubleshooting issues caused by
nondirect storage systems.
1.4.7 Installation Planning and Preparation
In preparation for an installation it is critical to review the below reference documents
and understand the information contained therein.
• version-specific hyperion Installation and Configuration guide
• version-specific hyperion Installation Start here
• version-specific hyperion rEADmE documents for each module (known
Issues)
• version-specific hyperion product patch sets from “my oracle Support”
1.4.8 Procure and Install Hardware per Sizing
Ensure the hardware is set up per your requirements. one common issue with virtual
environments is that the server administrators do not provide the resources requested.
Lack of proper resources will cause the installation to take additional time and also not
support real world user loads. The operating system the hyperion software is installed
on must see multiple cores to take advantage of Essbase's multithreaded design. Some
administrators may tell you one core is sufficient, this is not correct. testing the applica-
tion with a nontrivial amount of data and proper tuning will show this one core is far
out performed by many cores. Ensure at least four cores are allocated.
1.4.9 Firewalls and Load Balancers
If your environment will involve firewalls or load balancers, contact the appropriate
team weeks in advance of the installation to ensure the settings have been appropriately
modified to support your installation.
1.4.10 Sizing Guidelines
table 1.6 through table 1.10 are intended to help you to size a system quickly based on
a given number of users and set of applications. Performance testing using realistic user
cases is the best way to prove the system is working well. This being said, you can almost
always count on users to surprise you, especially when they all decide they need to use
the system on the last day of a financial cycle.
Table 1.6
Reporting (only) Essbase Server Sizing Guideline
Named Users
(Assumes 50% Load)
RAM/PAGE and
Number of Cubes
Cores
Data Drives
Supporting Servers
100 users
4
24 gB/12 gB; up
to 10 cubes
4-rAID 10
Single Server configuration. note
a single server configuration
limits your growth
250 users
8
48/24 gB; up to
32 cubes
8-rAID 10
Dedicated Web server(s)
750 users
12
192/48 gB; up to
128 cubes
12-rAID 10
Dedicated DB server
