Re: RAC One Node - Instances not open at the same time!
From: Martin Klier - Performing Databases GmbH <martin.klier_at_performing-db.com>
Date: Fri, 30 Jun 2017 09:29:00 +0200 (CEST)
Message-ID: <386374497.708.1498807740802.JavaMail.zimbra_at_performing-db.com>
Date: Fri, 30 Jun 2017 09:29:00 +0200 (CEST)
Message-ID: <386374497.708.1498807740802.JavaMail.zimbra_at_performing-db.com>
Niall,
the question is quite simple: How can I configure RAC One Node in a way that does not cause trouble for an application that's not RAC aware. Primary concerns:
- dbms_jobs running on two nodes the same time - utl_tcp sockets opened at the same time - sequences out of order
And again, I cannot change the (PL/SQL) application.
I can do everything I need with grid infrastructure plus a single instance, too. But that's not the topic. Because the major benefit for RAC One Node FOR ME is that I just have to configure the RAC OneNode service and I am done. No scripts to be written or no ora.* resources to modify. Anything else is fine, as long as it does no harm.
And before the topic comes up: No licensing worries.
Thanks
-- Martin Klier | Performing Databases GmbH Managing Partner | Senior DB Consultant Oracle ACE martin.klier_at_performing-db.com | https://www.performing-databases.com > Von: "Niall Litchfield" <niall.litchfield_at_gmail.com> > An: "Martin Klier - Performing Databases GmbH" <martin.klier_at_performing-db.com> > CC: "ORACLE-L" <oracle-l_at_freelists.org> > Gesendet: Donnerstag, 29. Juni 2017 17:44:39 > Betreff: Re: RAC One Node - Instances not open at the same time! > I don't see online relocation as the only benefit, automatic instance restarts > and automatic restart on another node when a node fails, or the db fails > multiple times on a single node are surely valuable as well. As I said I'm sure > I don't really understand the question. > On Thu, Jun 29, 2017 at 3:11 PM, Martin Klier - Performing Databases GmbH < > martin.klier_at_performing-db.com > wrote: >> Hi Niall, >> of course, but avoiding would take the benefits away. :) >> -- >> Martin Klier | Performing Databases GmbH >> Managing Partner | Senior DB Consultant >> Oracle ACE >> martin.klier_at_performing-db.com | https://www.performing-databases.com >>> Von: "Niall Litchfield" < niall.litchfield_at_gmail.com > >>> An: "martin klier" < martin.klier_at_performing-db.com > >>> CC: "ORACLE-L" < oracle-l_at_freelists.org > >>> Gesendet: Donnerstag, 29. Juni 2017 14:26:26 >>> Betreff: Re: RAC One Node - Instances not open at the same time! >>> I don't understand your question! The second instance is only up at the same >>> time as the first during an online relocation. In normal operation, including >>> failover/node loss, this is not the case. So just avoid using srvctl relocate >>> database :) >>> On Thu, Jun 29, 2017 at 12:24 PM, Martin Klier - Performing Databases GmbH < >>> martin.klier_at_performing-db.com > wrote:Received on Fri Jun 30 2017 - 09:29:00 CEST
>>>> Hi Listers,
>>>> when running Oracle RAC One Node, is there a way to avoid both instances being
>>>> open at the same time?
>>>> Background:
>>>> I have an application that's by no way ready for RAC (using dbms_jobs and much
>>>> more). But they want to use the benefits of One Node for operating the cluster.
>>>> All that's needed is a failover cluster.
>>>> Closest thing I can think of is to set the OnNode database to
>>>> -stopoption abort -timeout 0
>>>> but I am uncertain if that really makes sure that we have zero time with two
>>>> operational instances.
>>>> No need to point out that we could also use a single instance database: yes, I
>>>> know that, but this is about RAC One Node. :)
>>>> Thanks for all tips!
>>>> --
>>>> Martin Klier | Performing Databases GmbH
>>>> Managing Partner | Senior DB Consultant
>>>> Oracle ACE
>>>> martin.klier_at_performing-db.com | https://www.performing-databases.com
>>> -- >>> Niall Litchfield >>> Oracle DBA >>> http://www.orawin.info > -- > Niall Litchfield > Oracle DBA > http://www.orawin.info -- http://www.freelists.org/webpage/oracle-l