| Oracle® Fusion Middleware Installation Guide for Oracle Business Intelligence Applications 11g Release 1 (11.1.1.7) Part Number E35981-04 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Middleware Installation Guide for Oracle Business Intelligence Applications 11g Release 1 (11.1.1.7) Part Number E35981-04 |
|
|
PDF · Mobi · ePub |
This chapter describes the preinstallation and deployment requirements for Oracle BI Applications.
This section contains the following topics:
Section 2.1, "General Guidelines for Setting Up Databases for Oracle BI Applications"
Section 2.2, "Oracle-Specific Database Guidelines for Oracle Business Analytics Warehouse"
This section contains the following topics:
Section 2.1.1, "Guidelines for Oracle Business Analytics Warehouse Databases"
Section 2.1.2, "Why Use a Separate Database for the Oracle Business Analytics Warehouse?"
The following guidelines will help you set up the data warehouse physical database for performance and growth:
Allocate around 50 to 70 percent of the total available server memory to the database, assuming no other application is running on the same server.
At a minimum, separate the data and index tablespaces. Create more tablespaces to separate heavily used tables and their indexes.
Oracle recommends using 8k block size for Oracle warehouses. For more information about block size and Oracle databases, see the Oracle Database 11g Documentation Library on Oracle Technology Network.
If you are using multiple disk storage systems, stripe the tablespace containers and files across as many disks as possible.
Raw devices for tablespaces provide better performance as compared to cooked file systems.
RAID-5 is known to give a good balance of performance and availability.
Although it is technically possible to put the Oracle Business Analytics Warehouse in the same database as the transactional database, it is not recommended for performance reasons. The transactional database is structured as an online transaction processing (OLTP) database, whereas the Oracle Business Analytics Warehouse is structured as an online analytical processing (OLAP) database, each optimized for its own purpose. The reasons for not combining the two databases are the following:
ETL is configured to maximize hardware resources; and, therefore, the warehouse should not share any resources with any other projects.
The analytical queries interfere with normal use of the transactional database, which is entering and managing individual transactions.
The data in a transactional database is normalized for update efficiency. Transactional queries join several normalized tables and will be slow (as opposed to pre-joined, de-normalized analytical tables).
Historical data cannot be purged from a transactional database, even if not required for current transaction processing, because you need it for analysis. (By contrast, the analytical database is the warehouse for historical as well as current data.) This causes the transactional database to further slow down.
Transactional databases are tuned for one specific application, and it is not productive to use these separate transactional databases for analytical queries that usually span more than one functional application.
The analytical database can be specifically tuned for the analytical queries and Extract-Transform-Load (ETL) processing. These are quite different from transactional database requirements.
This section contains guidelines that are specific to Oracle databases, and contains the following topics:
This section contains additional suggestions for optimizing performance for Oracle databases.
Oracle BI Applications on Oracle databases support only binary sorting. If you are running an Oracle client, do one of the following:
Set the NLS_SORT parameter to BINARY.
Choose a NLS_LANG setting that includes binary.
These settings are required for adequate performance from the dedicated Web client.
It is recommended that you gather workload system statistics.
To increase data throughput between Oracle BI Server and the Oracle database, change SDU and TDU settings in listener.ora. The default is 2 KB and can be increased to 8 KB.
On the server side, edit the listener.ora file. Under the particular SID_LIST entry, modify SID_DESC as follows:
SID_LIST_LISTENER =
SID_LIST =
SID_DESC = (SDU=16384)(TDU=16384)
ORACLE_HOME = /.....)
SID_NAME = SOLAP)
)
)
Set the number of log file groups to 4.
On the client side, edit the tnsnames.ora file. Modify the TNS alias by adding SDU= and TDU= as follows:
myhost_orcl.world= DESCRIPTION=(SDU=16384)(TDU=16384) ADDRESS = (PROTOCOL = TCP)(HOST=myhost)(PORT=1521)) CONNECT_DATA=(SID=ORCL))
To configure the Business Analytics Data Warehouse on Oracle databases more easily, refer to the parameter template file init11gR2_template.ora file or init11gR2_Exadata_template.ora, which are stored in \<BI_Oracle_Home>\biapps\etl.
The parameter template file provides parameter guidelines based on the cost-based optimizer for Oracle 11gR2. Use these guidelines as a starting point. You will need to make changes based on your specific database sizes, data shape, server size (CPU and memory), and type of storage. The database administrator should make changes to the settings based on performance monitoring and tuning.
Copy the appropriate template file into your <ORACLE_HOME>/dbs directory. Then, review the recommendations in the template file, and make the changes based on your specific database configuration. The database administrator should make changes to the settings based on performance monitoring and tuning considerations.
Note:
The NLS_LENGTH_SEMANTICS parameter enables you to define byte- or character-length semantics. Oracle BI Applications supports BYTE and CHAR values for this parameter. If you are using MLS characters, then you can add this parameter to the parameter template file for your database version (that is, the init<DB version>.ora file).
|
 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|