Re: Oracle RAC with Active Data Guard : Maximum Availability Architecture
From: Radoulov, Dimitre <cichomitiko_at_gmail.com>
Date: Mon, 23 Dec 2013 16:29:57 +0100
Message-ID: <52B856F5.6080900_at_gmail.com>
On 23/12/2013 16:13, Nassyam Basha wrote:
> [...]
> 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.
Date: Mon, 23 Dec 2013 16:29:57 +0100
Message-ID: <52B856F5.6080900_at_gmail.com>
On 23/12/2013 16:13, Nassyam Basha wrote:
> [...]
> 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.
Even if you have FAN/TAF enabled, for applications using persistent connections, connection pools and batch jobs the maintenance of a single node is still some sort of "downtime" as it may imply the rollback of the current work and will require a new connection.
Regards
Dimitre
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Dec 23 2013 - 16:29:57 CET