High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

db_file_name_convert log_file_name_convert

edited Aug 19, 2013 6:57AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 6 commentsAnswered
It seems that when a copy of the production configuration was made on a non-prod environment the parameters were not modified to reflect the new environment.  that is db_file_name_convert and log_file_name_convert are still set in the parameter files, but they aren't accurate.  no conversion is needed in the non-prod environment.
1. do these parameter harm the dataguard?


2. can I just alter session set db_file_name_convert=(''); to empty the conversions?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center