Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 E-mail Us
 Oracle Articles
New Oracle Articles

 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog

 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Oracle Support

 SQL Tuning

 Oracle UNIX
 Oracle Linux
 Remote s
 Remote plans
 Application Server

 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S


 Consulting Staff
 Consulting Prices
 Help Wanted!


 Oracle Posters
 Oracle Books

 Oracle Scripts

Don Burleson Blog 







Data Guard parameters Tips

Oracle Database Tips by Donald BurlesonDecember 3, 2015

Oracle Data Guard Initialization Parameters

LOG_ARCHIVE_DEST_2='SERVICE=<Name of service for standby database>

The initialization parameter file for the Data Guard Oracle instance are essentially three key Data Guard parameters that should be added. These are as follows:

  • lock_name_space

  • db_file_name_convert

  • log_file_name_convert

These are the primary Data Guard init.ora parameters:

  • lock_name_space:  The lock_name_space parameter defines the namespace that the distributed lock manager uses to generate lock names. The value of the lock_name_space parameter should be set to a distinct value so that the lock names between the primary and the Oracle instance do not collide.

  • db_file_name_convert : The db_file_name_convert parameter is used to convert the filename on the primary database to a filename on the standby database. The value of db_file_name_convert  should be set in a pair of strings. The first string should correspond to the filename pattern on the primary database and the next string of db_file_name_convert to the filename pattern on the standby database. More than one pair can be specified in db_file_name_convert if there is a need to accommodate more than one pattern in filename changes between the primary and the standby database.

  • log_file_name_convert: The log_file_name_convert parameter works similarly to db_nfile_name_convert on the redo log files. Thielog_file_name_convert  parameter is not required until the Oracle instance is activated, but there is no harm in placing tlog_file_name_convert in your init.ora file so that during the activation there will be minimal work for you.

The following is a sample init.ora file for the Data Guard standby database. Note the change in the log file dump destinations:

# Diagnostics and Statistics

BACKGROUND_DUMP_DEST=/oracle/stdbydb/admin/bdump CORE_DUMP_DEST=/oracle/stdbydb/admin/cdump

# Control File Configuration


# Archive


# Miscellaneous



The above text is an excerpt from the book: Oracle Data Guard Handbook

Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster


Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


Copyright © 1996 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.