Re: db_unique_name
- From: goran bogdanovic <goran00@xxxxxxxxx>
- To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 31 May 2011 13:16:28 +0200
small off topic but also related to db_unique_name:
I have noticed when existing DG configuration is integrated into Oracle
Restart i.e. on one server runs primary on second standby, both DB's have
db_unique_name defined (e.g. db01 and db02), on standby server Oracle
Restart start standby database with SID=db_unique_name and not (as it should
be) with SID=db_name.
Anyone else has observed the same?
Any thoughts?
thanks,
goran
On Fri, May 27, 2011 at 10:37 PM, Emre Baransel <ebaransel@xxxxxxxxx> wrote:
> Hi
> Before 11gR1 it's not mandatory to use different db_unique_name on primary
> and standbys. Dataguard 11g admin guide says:
>
> Oracle Data Guard release 11g ensures each database's DB_UNIQUE_NAME is
> different. After upgrading to 11g, any databases with the same
> DB_UNIQUE_NAME will not be able to communicate with each other.
>
> Y. Emre Baransel
>
>
> ------------------------------
> *From:* K R <kp0773@xxxxxxxxx>
>
> *To:* Oracle-L@xxxxxxxxxxxxx
> *Sent:* Tuesday, May 24, 2011 9:47 PM
> *Subject:* db_unique_name
>
> All,
>
> I have the primary db on server A , and planning to make the standby on
> server B. Can I have the db_unique_name same same as db_name in standby
> database.?
>
> appreicate any suggestion.
>
> thanks
> Kart
>
>
>
>
>
>
>
Other related posts:
