Re: different service names on Standby
- From: George Leonard - Business Connexion <George.Leonard@xxxxxxxxx>
- To: "sethmiller.sm@xxxxxxxxx" <sethmiller.sm@xxxxxxxxx>
- Date: Mon, 1 Sep 2014 05:21:24 +0000
Hi
I can add: had a customer duplicate their prod to DR before, did not change
anything, and I mean nothing got changed, including the spfile, so service
names in there was the same,
Only difference was the hostname/ip's in the listener,
End result, the instances at DR tried to log into the service at production,
changing a 4 node RAC to have 4 working nodes and 4 nodes in recovery mode,
took a while to figure out what they did, so YE, I'm for changing service
names, especially which service (local and remote) to register with in the
spfile
and then as per everything mentioned before.
Yours Sincerely
________________________________________
George Leonard
Oracle Engineered System Specialist
Mobile: +27.82 655 2466
eMail: george.leonard@xxxxxxxxx<mailto:george.leonard@xxxxxxxxxx>
Web: http://www.bcx.co.za<mailto:george.leonard@xxxxxxxxxx>
[cid:6EA60917-E50D-422D-BF1F-E8C59EADC861]
On 28 Aug 2014, at 1:06 PM, Seth Miller
<sethmiller.sm@xxxxxxxxx<mailto:sethmiller.sm@xxxxxxxxx>> wrote:
Hemant,
I would in fact recommend defining different service names in your standby
databases, if for no other reason then you can easily identify to which
database you are connected at any given time. Another suggestion would be to
name the services in such a way as to identify the location, purpose and type
of the service, such as "london_oltp_oci". Including the type would only be
relevant if you are defining multiple services for different connection types
since they often require different settings for failover.
I always encourage DBAs to keep in mind that standby systems are separate
databases and they should be treated as such to minimize the chances of making
changes or connections to the wrong system accidentally. Therefore, I recommend
a different SID, different services names and a descriptive db unique name
(i.e. orcl_newyork and orcl_london rather than orcl and orcl_standby).
Seth Miller
On Thu, Aug 28, 2014 at 1:05 AM, Kim Berg Hansen
<kibeha@xxxxxxxxx<mailto:kibeha@xxxxxxxxx>> wrote:
We do have a different service name on the physical standby. The reason is it
is in "snapshot standby mode" during the day.
Our setup har three servers: db1, db2, db3
And three service names: dbP ("P"roduction), dbR ("R"eadonly), dbS ("S"andbox)
Normally dbP runs on db1, dbR on db2 and dbS on db3
One primary and two dataguard:
Service dbP is the primary.
Service dbR is Active DataGuard - failover as well as some queries for
reporting and extracting for dw
Service dbS is at 1AM switched to Physical Standby and at 5AM switched to
Snapshot Standby - test and training during the day, "refreshed" to a clone of
production during the night
But a DataGuard server that is Physical Standby all the time? I can't offhand
think of a reason for seperate service name? Unless for management purposes?
Regards
Kim Berg Hansen
http://dspsd.blogspot.com<http://dspsd.blogspot.com/>
kibeha@xxxxxxxxx<mailto:kibeha@xxxxxxxxx>
@kibeha
On Thu, Aug 28, 2014 at 5:38 AM, Chitale, Hemant K
<Hemant-K.Chitale@xxxxxx<mailto:Hemant-K.Chitale@xxxxxx>> wrote:
Just curious here ....
Other than for Active DataGuard ...
Would you define *different* service names on a Physical Standby ? (i.e.
service names that are not defined on the Primary).
Can you ? Why would you ?
(Active DataGuard I can understand : Useful to use a different service name
for Query sessions).
Hemant K Chitale
This email and any attachments are confidential and may also be privileged. If
you are not the intended recipient, please delete all copies and notify the
sender immediately. You may wish to refer to the incorporation details of
Standard Chartered PLC, Standard Chartered Bank and their subsidiaries at
https://www.sc.com/en/incorporation-details.html.
Other related posts:
