Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

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

DB_UNIQUE_NAME

Mar 20, 2013 8:56AM edited Mar 20, 2013 9:22AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 3 commentsAnswered

Hi,

Why we need to set different DB_UNIQUE_NAME on primary and standby database ?

I know 2 reasons to set different :

1) If both primary and standby database on same server.

2) if they are using ASM file system

Regards,

Nitesh Goel

0

Howdy, Stranger!

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

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

Category Leaderboard

Top contributors this month