Re: Oracle RAC with Active Data Guard : Maximum Availability Architecture

From: Nassyam Basha <>
Date: Mon, 23 Dec 2013 20:43:32 +0530
Message-ID: <>

Hi Chris,

Usually when patching on DataGuard environment, Standby will be down and patch will be applied(No post scripts will be updated), Next we jump to primary database and here its RAC so we can opt for rolling patching. in rolling patch there is no downtime at all. And each node will be patched and brought up while other node(s) are still running after all patching is done we do run post scripts..hence patching will be completed on primary.. So we can avoid downtime on Primary.

So far we initially already patched on standby and also primary, When patches are applied on whole environmnet, when we start MRP of course dictionary will be updated whenever the archives/redo applied on standby database(s). So still we can avoid downtime.

If you are planning for master patching, from 11g release to release (or) patch set upgrade, Then you might consider rolling upgrade patching. You can refer

In short i can say not complex, If properly planned :) Correct me if missing or something wrong.

Nassyam Basha.

On Mon, Dec 23, 2013 at 8:07 PM, Chris King <> wrote:

> We're architecting a new system, and will need 99.5% availability. Looking
> over Oracle's MAA options, I see RAC with Data Guard. .. but it's not clear
> to me how this would actually work to avoid ALL downtime. Won't I still
> need downtime to apply patches, even if I use rolling patches? And isn't it
> more complex applying patches when there's a standby involved?
> Is 99.5% really achievable with this combination?
> Thanks in advance..

Thanks & Regards,
Nassyam Basha.

Received on Mon Dec 23 2013 - 16:13:32 CET

Original text of this message