| |
 |
|
Donald K. Burleson
Oracle Tips |
Oracle and Disk Usage
AREA1. Executables, redo log files,
export files, a copy of the control file
AREA2. Data-datafiles, temporary user datafiles, a copy of the
control file, redo logs
AREA3. Indexes, a copy of the control file, redo logs
AREA4. Archive logs, rollback segments
Now we have succeeded in spreading I/O even further. Redo logs and
rollback segments have been separated; and because archive logs will
not be as active as redo logs, there will be less contention in this
configuration. In most installations, exports will be done during
off hours, therefore there should be little contention between the
redo logs and exports.
Five Areas (Shoehorn Required)
Well, this may not be Nirvana, but it is a minimum configuration.
Five areas allow OFA compliance and permit maximum spread of I/O
load. Let’s look at a five-area spread:
AREA1. Executables, a copy of the control file, redo logs, the
SYSTEM tablespace datafiles
AREA2. Data-datafiles, temporary user 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
Six Areas (Almost Enough)
We are getting closer with six available areas; we can move the
exports and temporary areas to their own disk now, eliminating that
source of contention, but what about backups?
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
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.
|
