8. What are the different options in Oracle for a good performing BW
system?
I/O hotspots:
The purpose of disk layout is to avoid I/O hot
spots by distributing the data accesses across several physical disks. The goal
is to optimize the overall throughput to the disks.
The basic rule is: stripe over everything, including RAID-subsystems.
Managing table spaces:Locally-Managed Table spaces manage their own extents
by maintaining bitmaps in each data file. The bitmaps correspond to (groups of)
blocks.
Be sure that all (bigger) table spaces are locally managed. Extent
and partition maintenance is drastically improved, as DB dictionary accesses are
minimized. Administration maintenance is also reduced.
Parallel query
option:
ORACLE can read database table contents in parallel if this setting
is active. BW uses this feature especially for staging processes and aggregate
build. The Parallel Query Option is used by default. Be sure, that the
init.ora-entries for PARALLEL_MAX_SERVERS are set appropriate to the
recommendations in the ORACLE note.
Table partitioning:
Table
partitions are physically separated tables, but logically they are linked to one
table name. PSA tables and non-compressed F-fact table are partitioned by the
system (by request ID). The (compressed) E-fact table can be partitioned by the
user by certain time characteristics. For range-partitioned InfoCubes, the SID
of the chosen time characteristic is added to both fact tables.
When using
range partitioning, query response time is generally improved by partition
pruning on the E fact table: all irrelevant partitions are discarded and the
data volume to be read is reduced by the time restriction of the query.
In
ORACLE, report SAP_DROP_EMPTY_FPARTITIONS can help you to remove unused or empty
partitions of InfoCube or aggregate fact tables. Unused or empty partitions can
emerge in case of selective deletion or aborted compression and may affect query
performance as all F fact table partitions are accessed for queries on the
InfoCube.
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/768773/viewspace-627551/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/768773/viewspace-627551/
本文探讨了在Oracle Business Warehouse系统中实现高效性能的方法,包括避免I/O热点通过合理分布数据访问,本地管理表空间以优化磁盘使用,启用并行查询选项以并行读取数据库内容,以及通过分区技术提高查询响应速度。

430

被折叠的 条评论
为什么被折叠?



