Oracle Repository Capacity Planning Issues with Hyperion Performance Suite

Oracle Repository Capacity Planning Issues with Hyperion Performance Suite [ID 583598.1]
		Modified 31-JAN-2012     Type HOWTO     Status ARCHIVED

In this Document
  Goal
  Solution

---

Applies to:

Hyperion Performance Suite
Information in this document applies to any platform.

Goal

Oracle Repository Capacity Planning Issues with Hyperion Performance Suite

Solution

Oracle Parameters for Performance Suite Repository database: 

db_block_buffers 2500
db_block_size 8192
log_buffer 163840
log_checkpoint_interval 10000
log_checkpoint_timeout 1800
processes 265
remote_login_passwordfile EXCLUSIVE
shared_pool_size 35389440

The recommendation is to separate the repository database to its own server/CPU with a dedicated schema. Small implementations (50 users) will require about 120 MB tablespace. Larger implementations may want to allow for 200 MB or more of tablespace using RAID or other high performance disk technologies to reduce the amount of time spent waiting for disk access. For example: RAID 0 striped across 3 internal disks, 32K stripe size. Also to improve performance create a larger data file initially otherwise pieces of it could be strewn across the disk.

A user must be created. This user owns the Hyperion Performance Suite database tables and objects that are built and populated during this installation. The user created here is also the user that Hyperion Performance Suite services use to connect to the database. Hyperion suggests naming the user 'hypsuite'. The Hyperion Performance Suite repository database user cannot be administrator. Appropriate database privileges are required to perform the following actions. To create the repository owner, enter the following commands from within the Oracle SQL*Plus utility as system/manager or other user with CREATE TABLESPACE system privileges:

create tablespace tablespace1 datafile 'hpsu1' size 150M;
create tablespace tablespace2 datafile 'hpsu1temp' size 15M;
create user hypsuite identified by password mypassword832 default tablespace tablespace1 temporary tablespace tablespace2;
grant connect, resource to hypsuite;

Ensure that the database allows plenty of connections from applications: roughly 50-75% of the number of concurrent active users. The particular database/schema should be dedicated solely to the Performance Suite repository.