Setting log_archive_dest_1 on standby to use OMF

Question

Hi,
I have a problem.
We initially setup a 2-node standby database from a 4 node primary. Initially all went well. We then configured DG Broker. There did not appear to be an issue, but now the Broker configuration seems to be "out of sync" with the "normal" data guard configuration.
We were not able to start the standby database, so we stopped the DG broker from running. We had then to change log_file_name_convert, db_file_name_convert (these were blanked out), FAL_SERVER (this was set to a single instance, and not the TWO TASK entry for the primary database).
We have also noticed that the archived log files used to be put in /reco/STBYDB/archivelog/YYYY_MM_DD. We did not have log_archive_dest_1 set originally, but when we removed the broker we saw this was set to /reco/STBYDB.
I'm basically looking at how to set the log_archive_dest_1 parameter to allow us to write the archive logs files into a seperate directory for each day.
The logs are being shipped and applied, I just want them to go back to the directory structure they used to go to.
I've tried unsetting log_archive_dest_1, setting it to location=USE_DB_RECOVERY_FILE_DEST. It's currently set to /reco/STBYDB/archivelog and the files are being written to that directory.

Answer 1

Hello;
This is probably caused by mixed SQL with Broker commands. Once you start using broker you need to just use broker.
When you set values for database properties in the broker configuration, the broker records the change in the configuration file and propagates the change to all of the
databases in the Data Guard configuration. See - Data Guard Broker 11g Release 2 (11.2) E17023-06 "Update Database Properties, As Needed"
I would consider removing broker, getting my database parameters in order and then setting up broker again.
If you go this route FRA is your friend :
alter system set db_recovery_file_dest='/u01/app/oracle/flash_recovery_area';
alter system set log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST';
How to Safely Remove a Data Guard Broker Configuration [ID 261336.1]
Best Regards
mseberg