Versions Compared

Version Old Version 2 New Version 3
Changes made by

Jan Klinke

Jan Klinke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Location of OMF files on standby server is completely driven by OMF parameters db_create_file_dest , db_create_online_log_dest_[x] and db_recovery_file_dest. You may change it to place your files on different ASM diskgroup, different filesystem mountpoint etc … OMF parameters on primary and standby are needed even if you don’t make any type of name/path conversion.

...

OMF init parameters are:

Code Block
db_create_
online
file_
log_dest_1 = /u02/app/oracle/oradata/DEV, you would end up with nonsense path: /u02/app/oracle/oradata/DEV/DEV/onlinelog/o1_mf_3_lw9or7g1_.log

If you have identical filesystem structure on standby and on primary (no path conversion done):

  • You will need to set OMF parameters when creating standby database to the same values as on your primary

Note
Code Block
OMF parameters db_create_file_dest, db_recovery_file_dest or 
dest                 
db_create_online_log_dest_1          
db_create_online_log_dest_2
db_create_online_log_dest_3
db_create_online_log_dest_4
db_create_online_log_dest
_[x] are needed even if your standby file locations are the same as on primary. They will be automatically copied from your current primary database init parameters during create standby database process.

If you would like to have different file paths on primary and standby or if you’re converting between ASM and filesystem (path conversion is done):

  • You will need to set OMF parameters when creating standby database to intended locations

OMF init parameters are:

db_create_file_dest                 
db_5
Info

Don’t forget that Oracle automatically adds db_unique_name to the OMF path. Never set OMF parameters to contain any actual name. For example if you would set db_create_online_log_dest_1

db_create_online_log_dest_2 db_create_online_log_dest_3 db_create_online_log_dest_4

= /u02/app/oracle/oradata/DEV, you would end up with nonsense path: /u02/app/oracle/oradata/DEV/DEV/onlinelog/o1_mf_3_lw9or7g1_.log

If you have identical filesystem structure on standby and on primary (no path conversion done):

  • You will need to set OMF parameters when creating standby database to the same values as on your primary

Note

OMF parameters db_create_file_dest, db_recovery_file_dest or db_create_online_log_dest_

5

[x] are needed even if your standby file locations are the same as on primary. They will be automatically copied from your current primary database init parameters during create standby database process.

If you would like to have different file paths on primary and standby or if you’re converting between ASM and filesystem (path conversion is done):

  • You will need to set OMF parameters when creating standby database to intended locations

For each type of file OMF rules are applied differently:

...