Call (800) 766-1884 for Oracle support & training
Free Oracle Tips

Oracle Consulting Support
Oracle Upgrades
Use New Oracle Features
Oracle Replication Support
Oracle Training
Remote Oracle DBA
System Documentation
Oracle Tips
Oracle Performance

Free Oracle Tips



BC Oracle tuning

Oracle training

Oracle support

Remote Oracle



  Oracle Tips by Burleson

Minimum Oracle OFA Configuration

The minimum suggested configuration would consist of seven data areas: 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 disk 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-datafiles, a control file, tool-datafiles, redo logs
AREA3. Index-datafiles, a control file, redo logs
AREA4. Rollback segment-datafiles
AREA5. Archive log files
AREA6. Export files
AREA7. Backup staging

Of course, this is just a start; you might find it wise to add more areas to further isolate large or active tables into their own areas as well as to separate active index areas from each other.
The structure on UNIX could look like the following:

/oracle0/product/oracle/9.0.1/ Top level $ORACLE_HOME
bin/ Standard distribution structure under version
/oracle0/data/ Place instance names under type directories
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

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/9.0.1 directory becomes c:\oracle0\product\oracle\9.0.1\.

I have seen several questions posted as to why the standard says to use u01, u02, and so on for mount points. This based in old UNIX naming conventions and has little actual usefulness in modern structures. Call the mount points whatever you wish as long as it meets your requirements. I suggest using the application name, for example.

This is an excerpt by Mike Ault’s book “Oracle Administration & Management”.  If you want more current Oracle tips by Mike Ault, check out his new book “Mike Ault’s Oracle Internals Monitoring & Tuning Scripts” or Ault’s Oracle Scripts Download.

Download your Oracle scripts now:

The definitive Oracle Script collection for every Oracle professional DBA


Oracle performance tuning software 

Oracle performance tuning book


Oracle performance Tuning 10g reference poster
Oracle training in Linux commands
Oracle training Excel
Oracle training & performance tuning books



Copyright © 1996 -  2014 by Burleson. All rights reserved.

Oracle® is the registered trademark of Oracle Corporation.