RE: RAC clarifications
From: D'Hooge Freek <Freek.DHooge_at_uptime.be>
Date: Sat, 19 Dec 2009 14:38:17 +0100
Message-ID: <4814386347E41145AAE79139EAA398980DB6EDAB2C_at_ws03-exch07.iconos.be>
About the patching. Most of the patches seems to be rolling upgrades, which means that no entire cluster downtime is required. But you still need to stop the instances/clusterware node per node. And here lies the problem, most applications are not rac "aware" and can't transparent deal with the failover of a session from one node to another (which is also the reason why so many applications still have some downtime when a rac node fails). The same applies for dataguard.
Date: Sat, 19 Dec 2009 14:38:17 +0100
Message-ID: <4814386347E41145AAE79139EAA398980DB6EDAB2C_at_ws03-exch07.iconos.be>
About the patching. Most of the patches seems to be rolling upgrades, which means that no entire cluster downtime is required. But you still need to stop the instances/clusterware node per node. And here lies the problem, most applications are not rac "aware" and can't transparent deal with the failover of a session from one node to another (which is also the reason why so many applications still have some downtime when a rac node fails). The same applies for dataguard.
If your application properly supports fan/fcf, then you will need very little maintenance downtime with rac. I if doesn't, then you probably will need more downtime (more layers to patch) then with a single node configuration (in which case dataguard may be a better solution).
Regards,
Freek D'Hooge
Uptime
Oracle Database Administrator
email: freek.dhooge_at_uptime.be
tel +32(0)3 451 23 82
http://www.uptime.be
disclaimer: www.uptime.be/disclaimer
-- http://www.freelists.org/webpage/oracle-lReceived on Sat Dec 19 2009 - 07:38:17 CST