| ||||||||||||||||||||||||||||||||||||||
|
Optimal Flexible Architecture (OFA)Optimal Flexible Architecture provides a logical physical layout for the database that helps the DBA to manage the system. In addition, a properly configured Oracle instance will minimize contention thus improving performance. Perhaps one of the most overlooked tuning option, configuration, must utilize OFA guidelines to be successful.
In accordance with Cary V. Millsap of the Oracle National Technical Response Team, the OFA process involves following 3 rules:
1. Establish an orderly operating system directory structure in which any database file can be stored on any disk resource.
2. Separate groups of segments (data objects) with different behavior into different tablespaces.
3. Maximize database reliability and performance by separating database components across different disk resources. A caveat for RAID environments, consider also spread across controller volume groups.
Minimum OFA ConfigurationThe minimum suggested configuration would consist of seven data areas, either disks, striped sets, RAID sets, or whatever else comes down the pike in the next few years. These areas should be as separate as possible, ideally operating off of different device controllers or channels to maximize throughput. The more heads you have moving at one time, the faster your database will be. The disk layout should minimize disk contention. For example: · AREA1: Oracle executables and user areas, a control file, the SYSTEM tablespace, redo logs · AREA2: Data-data files, a control file, tool-data files, redo logs · AREA3: Index-data files, a control file, redo logs · AREA4: Rollback segment-data files · AREA5: Archive log files · AREA6: Export Files · AREA7: Backup Staging
Of course, this is just a start, you mind find it wise to add more areas to further isolate large or active tables into their own areas as well as separating active index areas from each other. Note that on a modern system this configuration may require 4-2 channel controller cards and 8 physically separable disk arrays. The structure on UNIX could look like the following: /oracle0/product/oracle/8.1.3/ Top level $ORACLE_HOME bin/ Standard distribution structure under version doc/ rdbms/ … /oracle0/data/ Place instance names under type directories ortest1/ ortest2/ /oracle0/control/ ortest1/ ortest2/ /oracle0/redo/ ortest1/ ortest1/ /oracle0/admin/ ortest1/ bdump/ backup_dump_dest udump/ user_dump_dest cdump/ core_dump_dest pfile/ initialization file location (linked back to dbs directory) create/ Database creation script storage area ortest2/ … /oracle1/data/ /control/ /redo/ /oracle2/data/ /control/ /redo/ … /oracle7/data/ /control/ /redo/
Using this type of structure even on a RAID5 volume allows for a logical separation of files for ease in locating and controlling database files. For other platforms just alter the directory syntax for example on NT the "/oracle0/product/oracle/8.1.3" directory becomes "c:\oracle0\product\oracle\813\".
The above text is an excerpt from Mike Ault’s Oracle DBA Made Simple by Rampant TechPress.
Oracle9i RAC
Oracle9i
RAC is the first-of-its-kind reference for Real Application
Clusters (RAC) and TAF technology. Learn from the experts how to quickly
optimize your Oracle clustered server environment for optimal performance
and flexibility. Covering all areas of RAC continuous availability and
transparent application failover, this book is indispensable for any
Oracle DBA who is charged with configuring and implementing a RAC clusters
database.
http://www.rampant-books.com/book_2003_1_rac.htm
|
| ||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||