| |
 |
|
Donald K. Burleson
Oracle Tips |
Oracle and Disk Usage
AREA3. Index datafiles, a copy of the
control file, redo logs
AREA4. Rollback segment datafiles, export files
AREA5. Archive log files
AREA6. Temporary areas, export files
Seven Areas (Oracle Nirvana)
With seven areas we have minimum contention; and by moving export
files to tape, we can eliminate one additional source of database
lockup.
AREA1. Executables, a copy of the control file, redo logs, the
SYSTEM tablespace datafiles
AREA2. Data-datafiles, a copy of the control file, redo logs
AREA3. Index datafiles, a copy of the control file, redo logs
AREA4. Rollback segment datafiles, export files
AREA5. Archive log files
AREA6. Temporary areas, export files
AREA7. Backup staging area
By monitoring AREA5 and periodically removing archive log files to
tape we can eliminate another. If we really wanted to push OFA, we
could add a couple of areas for redo logs. Of course, if you use the
partitioning options of Oracle, then you may need many more areas in
order to place the partitions in separate areas.
Other authors recommend larger configurations, and in some cases
they are warranted. If you have several large tables, consider
placing these, and their indexes, in separate areas. Most of this
type of consideration is application-dependent. With some of the
giant databases we are now seeing (hundreds of gigabytes aren’t
uncommon anymore) and with petabyte sizes now available through the
latest releases of Oracle, it seems silly to talk about a mere 5, 7,
or 100 disks. If you can use RAID0/1 and stripe data across multiple
platters, do it. Of course, don’t do what one inexperienced system
administrator did: try to do RAID5 sets with two disks each.
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.
|
