Re: why are some applications oracle but not RAC compatible?
- From: timhall1@xxxxxxxxx
- To: andrew.kerber@xxxxxxxxx,ckaj111@xxxxxxxx
- Date: Wed, 26 Mar 2014 18:38:21 +0000
One subtle application design issue that can trip up a RAC installation is
using sequence-generated IDs as "tie-breakers" in ORDER BY clauses in queries
(since each node would cache a range of numbers at a time, the values are no
longer guaranteed to be deployed in numerical order).
HTH
Sent via BlackBerry from T-Mobile
-----Original Message-----
From: Andrew Kerber <andrew.kerber@xxxxxxxxx>
Sender: oracle-l-bounce@xxxxxxxxxxxxx
Date: Wed, 26 Mar 2014 13:33:08
To: <ckaj111@xxxxxxxx>
Reply-To: andrew.kerber@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx<oracle-l@xxxxxxxxxxxxx>
Subject: Re: why are some applications oracle but not RAC compatible?
I am not sure how you would make something incompatible with RAC. But it
is not hard to design an app that is not RAC aware. For example, you could
write something that will does not understand fail over. You could also
write something that expects to connect only to a specific instance I
suppose. If your connection methodology requires connection to an instance
instead of a service, you would not be able to take advantage of load
balancing. Perhaps there is a way to make software incompatible with RAC, I
would be interested to hear what it is.
On Wed, Mar 26, 2014 at 1:14 PM, Chris King <ckaj111@xxxxxxxx> wrote:
> Can anyone tell me why an application would be compatible with oracle but
> not rac? I'm assuming it must have to do with connectivity, but not sure
> why that isn't transparent to all applications?
>
> Thanks in advance.
>
>
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
Other related posts:
