3.

5 Additional Suggestions for Optimizing Oracle Performance in Oracle Business

Analytics Warehouse
This section contains additional suggestions for optimizing performance.
Oracle Business Intelligence Applications under Oracle support only binary sorti
ng. 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 clie
nt.
Make sure that cost-based optimization is enabled in the Oracle development, tes
t, and production databases and that statistics are kept up to date. Otherwise,
the rule-based optimizer may be used.
Create foreign keys in the Oracle database, but configure Oracle to not enforce
the foreign key relationship. The existence of foreign keys will allow Oracle to
better optimize certain queries. By turning off enforcement, the database load
should not be negatively affected.
Analyze application for occurrences of highly skewed data that is indexed. Creat
e histogram statistics for these indices to enable the optimizer to better perfo
rm queries.
To increase data throughput between Oracle BI Server and Oracle, 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 en
try, modify SID_DESC as follows:
SID_LIST_LISTENER =
SID_LIST =
SID_DESC = (SDU=16384)(TDU=16384)
ORACLE_HOME = /.....)
SID_NAME = SOLAP)
)
)
Set the tablespace to at least the same as the transactional database size. Make
sure the temporary tablespace has adequate space.
Set the number of log file groups to 4.
Set the size of each log file to 10 MB.
The sga_max_size to 700 MB.
On the client side, edit the tnsnames.ora file. Modify the TNS alias by adding S
DU= and TDU= as follows:
myhost_orcl.world=
DESCRIPTION=(SDU=16384)(TDU=16384)
ADDRESS = (PROTOCOL = TCP)(HOST=myhost)(PORT=1521))
CONNECT_DATA=(SID=ORCL))