Detections
Analytics
O19C-00-020500 - A minimum of three Oracle Control Files must be created and each stored on a separate physical and logical device.
Information
Oracle control files store information critical to Oracle database integrity. Oracle uses these files to maintain time synchronization of database files and verify the validity of system data and log files at system startup. Loss of access to the control files can affect database availability, integrity, and recovery.Oracle Pluggable Databases (PDBs) do not contain their own control files; instead, all PDBs within a Container Database (CDB) share control files managed by the CDB.
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
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.
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Oracle_Database_19c_V1R3_STIG.zip
Item Details
Audit Name: DISA Oracle Database 19c STIG v1r3 OracleDB
Category: CONFIGURATION MANAGEMENT
References: 800-53|CM-6b., CAT|II, CCI|CCI-000366, Rule-ID|SV-275999r1115962_rule, STIG-ID|O19C-00-020500, Vuln-ID|V-275999
Plugin: OracleDB
Control ID: 904d91d8ef384bdb434f58d79c87828e5be8cadb0b1237dfd0a623372ec3d22c