RE: Failover to another site Full DR.

We did this with a 'floating' ip that we could switch between servers.
Clients would all just point to the floating ip, so when we'd do a
dataguard switchover/failover, the clients would only notice a blip and
life would carry on (not quite RAC-like, but close).  Best to have the
IP switch included in your switchover scripts.  We've used it to good
effect here.

- Chris

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Goulet, Richard
Sent: Thursday, January 29, 2009 3:45 PM
To: howard.latham@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: Failover to another site Full DR.

An answer that I used with some success was to add a second address line
to the TNSNAMES.ora.  When the primary was out of commission the users
would connect automatically to the backup. 


Dick Goulet


-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Howard Latham
Sent: Thursday, January 29, 2009 4:40 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Failover to another site Full DR.

Oracle 11 - Redhat Linux 64bit
How do you failover over in dataguard/(AKA Log shipping)  to another
site with a completely different IP range.?

Where does a users url get redirected ? and what about ip addresses /
host names on their pcs?

It seems to me there is going to be a single point of failure whatever
you do.

And has anybody written a manual that enables a non dba to do a
failover ? ( I'm guessing not!)

-- 
Howard A. Latham
--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l

Other related posts: