Donald K. Burleson
Oracle Optimal Flexible
You may wish to add an additional directory layer if you will have
multiple Oracle versions running at the same time. This additional
layer includes the version level.
2. Separate groups of segments (data objects) with different
behavior into different tablespaces.
* Separate groups of objects with different fragmentation
characteristics in different tablespaces (e.g., don’t put data and
rollback segments together).
* Separate groups of segments that will contend for disk resources
in different tablespaces (e.g., don’t put data and indexes
* Separate groups of segments representing objects with differing
behavioral characteristics in different tablespaces (e.g., don’t put
tables that require daily backup in the same tablespace with ones
that require yearly backup).
3. Maximize database reliability and performance by separating
database components across different disk resources. A caveat for
RAID environments: Consider spreading datafiles across multiple
controller volume groups.
* Keep at least three active copies of a database control file on at
least three different physical arrays.
* Use at least three groups of redo logs in Oracle. Isolate them
to the greatest extent possible on hardware serving few or no files
that will be active while the RDBMS (relational database management
system) is in use. Shadow redo logs whenever possible.
* Separate tablespaces whose data will participate in disk resource
contention across different physical disk resources. (You should
also consider disk controller usage.)
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.
Copyright © 1996 - 2014 by
Burleson. All rights reserved.
Oracle® is the registered trademark
of Oracle Corporation.