Rule ID
SV-219827r879887_rule
Version
V2R9
CCIs
Oracle control files are used to store information critical to Oracle database integrity. Oracle uses these files to maintain time synchronization of database files as well as at system startup to verify the validity of system data and log files. Loss of access to the control files can affect database availability, integrity and recovery.
From SQL*Plus:
select name from v$controlfile;
DoD guidance recommends:
2a. Each control file is to be located on separate, archived physical or virtual storage devices.
OR
2b. Each control file is to be located on separate, archived directories within one or more RAID devices.
3. The Logical Paths for each control file should differ at the highest level supported by the configuration, for example:
UNIX
/ora03/app/oracle/{SID}/control/control01.ctl
/ora04/app/oracle/{SID}/control/control02.ctl
Windows
D:/oracle/{SID}/control/control01.ctl
E:/oracle/{SID}/control/control02.ctl
If the minimum listed above is not met, this is a finding.
Consult with the SA or DBA to determine that the mount points or partitions referenced in the file paths indicate separate physical disks or directories on RAID devices.
Note: Distinct does not equal dedicated. May share directory space with other Oracle database instances if present.To prevent loss of service during disk failure, multiple copies of Oracle control files must be maintained on separate disks in archived directories or on separate, archived directories within one or more RAID devices. Adding or moving a control file requires careful planning and execution. Consult and follow the instructions for creating control files in the Oracle Database Administrator's Guide, under Steps for Creating New Control Files.