 |
Distributing files across disk
drives ensures optimum performance by separating files that Oracle needs
to access parallely. This table recommends the data files to be located
on disks when different numbers of disks are used.
Total
Number of Disk Drives |
Disk
Drive Number |
Database
Files |
5 |
1 |
users1.dbf, control1.ctl, system.dbf, tools1.dbf,
redo1.dbf, redo2.dbf, redo3.dbf. redo4.dbf
|
2 |
cisdb1.dbf, control2.dbf
|
3 |
cisindex1.dbf, control3.ctl
|
4 |
undo1.dbf
|
5 |
arch/, bdump/, cdump/, udump/, temp1.dbf,
cisdb_rot1.dbf
|
4 |
1 |
users1.dbf, control1.ctl, system.dbf, tools1.dbf,
redo1.dbf, redo2.dbf, redo3.dbf, redo4.dbf
|
2 |
cisdb1.dbf, control2.dbf
|
3 |
cisindex1.dbf, control3.ctl
|
4 |
undo1.dbf, arch/, bdump/. cdump/, udump/,
temp1.dbf,cisdb_rot1.dbf
|
3 |
1 |
users1.dbf, control1.dbf, system.dbf, tools1.dbf,
redo1.dbf, redo2.dbf, redo3.dbf, redo4.dbf, cisdb_rot1.dbf
|
2 |
cisdb1.dbf, control2.ctl, temp1.dbf
|
3 |
cisindex1.dbf, control3.ctl, arch/, bdump/,
cdump/, udump/
|
2 |
1 |
users1.dbf, control1.dbf, control2.dbf, system.dbf,
tools1.dbf, redo1.dbf, redo2.dbf, redo3.dbf, redo4.dbf, undo1.dbf,
cisindex1.dbf
|
2 |
cisdb1.dbf, control3.ctl, temp1.dbf, arch/,
bdump/, cdump/, udump/, cisdb_rot1.dbf
|
The recommendations made in the
table reflect the following basic considerations. This approach can be followed
both for UNIX and Windows:
- Spreading files across several physical disk drives reduces disk
I/O contention.
- Reducing disk I/O contention ensures maximum database throughput
and benefit from oracle's read-ahead operations.
- The more disk heads moving at one time, faster is the database fetch.
- Index files should be on a separate physical disk drive from the
database data files.
- High-volume, high-activity files should be on separate high-speed
physical disk drives.
|