RE: Oracle High Availability Question(s)

From: Scott Canaan <>
Date: Wed, 14 Feb 2018 21:24:31 +0000
Message-ID: <>

We are on, looking to upgrade to

Scott Canaan ’88 (<>)

(585) 475-7886 – work                (585) 339-8659 – cell
“Life is like a sewer, what you get out of it depends on what you put into it.” – Tom Lehrer

From: [] On Behalf Of Andrew Kerber Sent: Wednesday, February 14, 2018 4:14 PM To: Cc: ORACLE-L
Subject: Re: Oracle High Availability Question(s)

It might be worth the investment to do some serious learning on data guard. There is a lot of capability there, and it sounds like you arent using most of it. At the very least, you can set up a failover type tns entry, with a single service name. Oracle dataguard can be configured to move the service name to the read-write instance. What oracle version are you on?

On Wed, Feb 14, 2018 at 3:00 PM, Rich J <<>> wrote:

On 2018/02/14 14:39, Scott Canaan wrote: We are currently using Data Guard and we hate it. It’s the only place we use it and we were never given any training on it, so we threw it together as best we could. Every time we have to do anything with it (including patching), we pray that it will recover and continue working. What we have proposed is to go to Linux clustering instead, eventually going to Libvert, eliminating the Data Guard and moving the fault tolerance to the cluster. The app is not Data Guard aware, so when a failover does occur, the app stops working until someone manually points it to the other server and restarts it. Linux clustering would solve that problem. If Linux clustering is an option, perhaps a multi-node hyper-converged solution like ones from Simplivity or Nutanix is also an option? I'm not sure that gets you out of the Data Guard game though, depending on how you're using it. I only mention that because I'm looking in that direction for a possible platform migration myself, and we have ADG. Rich


Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'
-- Received on Wed Feb 14 2018 - 22:24:31 CET

Original text of this message