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

MOSC Banner

Migrate using Physical StandBy - ASM - DB_UNIQUE_NAME

edited Dec 3, 2014 10:12AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 1 commentAnswered

Hi gurues,

I want to migrate a database using Physical StandBy. But as DB_UNIQUE_NAME between a primary and secundary is different, the ASM directory (+DATA/DB_UNIQUE_NAME) is different, so, when I will execute the switchover command the ASM directory will be different of the new ORACLE_SID.

For example:

Previous Switchover

PRIMARY:

db_unique_name = PROD

ASM directory = +DATA/PROD

SECONDARY:

db_unique_name = STDBY

ASM directory = +DATA/STDBY

After Switchover

EX-PRIMARY:

db_unique_name = STDBY

ASM directory = +DATA/PROD

EX-SECONDARY

db_unique_name = PROD

ASM directory = +DATA/STDBY

So, I would like the ASM directory will be the same for both environment, it is possible?

Tagged:

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