Re: Moving to RAC`

From: Stojan Veselinovski <stojan.veselinovski_at_gmail.com>
Date: Wed, 4 Mar 2015 09:56:28 +1100
Message-ID: <CALn1tDsHAQ6QENUUxsu396H4M40jK_y6cvByr3_eJH3LZaO4EQ_at_mail.gmail.com>



Agree with Jeremy's sentiments.

The initial stages you are likely to get less fault tolerance due to configuration, bugs, learnings etc, etc, RAC is not a magic HA bullet. Make sure you properly design and architect for it.

Make sure you test load and resilience eg. downing nics in bonded interfaces or haip, node evictions, losing io channel, etc, etc

Stojan
www.stojanveselinovski.com/blog
www.stojanveselinovski.com

>
> On a related note - your business thinks they will get "fault
> tolerance" - but make sure they understand the app might need to be
> restarted if there's a RAC node failure. Many businesses don't
> realize that their app might still need a restart (causing some
> downtime and all users to lose work and logon again). The app can be
> coded by developers to avoid this restart (utilizing TAF and
> callbacks). Version 12c provides a new feature called application
> continuity to avoid the coding part, but (1) this is brand new and
> should have thorough in-house testing before your business relies on
> it and (2) it has its own requirements (like a specific client driver)
> which your app needs to meet.
>
>
> -Jeremy
> --
> http://about.me/jeremy_schneider
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Tue Mar 03 2015 - 23:56:28 CET

Original text of this message