We recommend that you store the files of the database system on different physical disks. In this example, the control file is mirrored twice:
Disk Number |
Directory |
Contents of Directory |
---|---|---|
1 |
origlogA |
Online redo log files from the first and third group (Set A) |
2 |
origlogB |
Online redo log files from the second and fourth group (Set B) |
3 |
mirrlogA |
Mirrored online redo log files from the first and third group (Set A) |
4 |
mirrlogB |
Mirrored online redo log files from the second and fourth group (Set B) |
5 |
sapdata1 |
Database files, mirror of the control file |
6 |
sapdata2 |
Database files, mirror of the control file |
7 |
sapdata<n> |
Other database files in sapdata3 up to sapdata<n>, each on separate disks when possible |
A disk assignment similar to this is essential for reliable database operation. For performance reasons, we recommend you to distribute the online redo log groups to four disks, as shown above.
Make sure that the number and descriptions of the control file and its mirrors agree with the entry in the init<DBSID>.ora profile or spfile.
The database files can be distributed across any number of disks.
Make sure that the offline redo log files (that is, online redo log files saved to the archive directory) are not stored on the same disk as the online redo log files.
The offline redo log files are not shown in the above example.