Is log_archive_config parameter mandatory parameter to specify in Dataguard configiration.
I have set up a DR without specifying this parameter and it works fine with no problem whatsoever.
No. ( the short simple answer )
It has a default like many other parameters :
The default works fine for Data Guard. ( 'SEND, RECEIVE, NODG_CONFIG' )
Oracle docs say "Highly recommended." See chapter 14 for details - E10700-02
However if you run in Maximum Availability you will probably be glad you can it set. Add the database unique names of the other databases. By setting it you can avoid many issues in a RAC setup.
Please consider closing some of your old questions.
Total Questions: 69 (21 unresolved)
Edited by: mseberg on Mar 4, 2013 2:55 PM
*184.108.40.206 Automatic Repair of Corrupt Data Blocks* If a corrupt data block is discovered on a physical standby database, the server attempts to automatically repair the corruption by obtaining a copy of the block from the primary database if the following database initialization parameters are configured on the standby database: The LOG_ARCHIVE_CONFIG parameter is configured with a DG_CONFIG list and a LOG_ARCHIVE_DEST_n parameter is configured for the primary database. or The FAL_SERVER parameter is configured and its value contains an Oracle Net service name for the primary database
What I'm trying to say is on RAC it is very important. On Non-RAC, single Primary and Standby you should not see any adverse repercussions if you don't set it.
It's important on RAC because of the the extra pieces to that setup.