Oracle Study Notes: The db_create_file_dest parameter is really good

The official statement of the db_create_file_dest parameter is to enable management based on Oracle-managed files (OMF. OMF Management of Redo, control, temp, undo, and data files

My understanding is that it is neither safe nor nice to let Oracle put all the files in the default location! Therefore, Oracle releases this parameter to allow users to specify the storage location of various files. But to increase the mystery, the file name should be changed to a certain rule!

 

Similarly, the db_recovery_file_dest parameter enables OMF Management of Redo, control, RMAN backups, archived logs, and flashback logs files.

Similarly, the db_create_online_log_dest_n parameter enables OMF Management of redo and control.

 

We can also see the importance of redo and control files !! The effect of these three parameters on the location of the redo and control files:

1. Location priority: [control_files initialization parameter>] db_create_online_log_dest_n> db_recovery_file_dest> = db_create_file_dest

The equal sign here is interesting: If there is no signature and db_create_file_dest exists, db_recovery_file_dest is equivalent to db_create_online_log_dest_2, and db_create_file_dest is equivalent

2. Redo file multiplexing

You should specify db_create_online_log_dest_n to achieve this goal!

3. What if the three parameters specify the same value?

Guess it yourself :)

4. Naming rules for OMF files

<_ DEST _ parameter path>/<db_unique_name_or_db_name>/<datafile>/o1_mf _ % T _ % u _. DBF