There is a problem with this approach
that may only become apparent at high
concurrency.
Since you are operating with two-phase
commits, you may come up against the case
where writers block readers.
Your client issues a commit to both servers.
Each server get the PREPARE message,
and when both
Jonathan,
Thanks for this valuable information.
However, I'm using regular commits, not distributed two-phased ones and I
just have simple code to handle the situation where servers return different
success/error codes.
Tanel.
There is a problem with this approach
that may only become
Tanel,
If this is the approach, then quite a bit of code would have to be developed on the front end to handle transaction integrity. For example when one fails and the other has completed the write successfully, they will have to be physically removed.What about if the record that is commited
-358-8211 x 359
http://www.gridapp.com
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Tanel Poder
Sent: Monday, December 15, 2003 6:29 AM
To: Multiple recipients of list ORACLE-L
Subject: Re: Re: 24 x 7 x 365
Jonathan,
Thanks for this valuable
Tanel,
I think this is a good solution, provided the application can handle two phased commit protocol across both the databases, else there could be orphan records on one or both these databases.
Murali Tanel Poder [EMAIL PROTECTED] wrote:
When you want true 24x7 without compromises, then you
If this is the customer you are talking about, this database supports over 12 million subscribers..
Murali Tim Gorman [EMAIL PROTECTED] wrote:
As I mentioned a few minutes ago in another thread, there is an application using Oracle Rdb on an HP OpenVMS cluster located at HP in Colorado Springs
AM
Subject: Re: 24 x 7 x 365
If this is the customer you are talking about, this database supports
over 12 million subscribers..
Murali Tim Gorman [EMAIL PROTECTED] wrote:
As I mentioned a few minutes ago in another thread, there is an
application using Oracle Rdb on an HP
Yep, I also think so. I'm currently developing a small prototype for this kind of
transparent proxy, which I'll post here when it's stable...
Tanel.
Tanel,
I think this is a good solution, provided the application can handle
two phased commit protocol across both the databases, else there
Well, first
thing that needs to be noted is that 24 x 7 x 365 indicates
uptime for 7 years, which always gives me a chuckle when people say it. Mind you, Ive been guilty of
saying it too! J
And probably
the second thing that needs to be said is that no single product addresses true
HA
Title: RE: 24 x 7 x 365
As 2004 is a Leap Year, in February you have a one day window of opportunity to do upgrades. ;-)
Jerry Whittle
ASIFICS DBA
NCI Information Systems Inc.
[EMAIL PROTECTED]
618-622-4145
-Original Message-
From: Tracy Rahmlow [SMTP:[EMAIL PROTECTED]
Sent
You mean 2004/02/31, the 31st of February?
On 12/10/2003 02:19:34 PM, Whittle Jerome Contr NCI wrote:
As 2004 is a Leap Year, in February you have a one day window of opportunity to do
upgrades. ;-)
Jerry Whittle
ASIFICS DBA
NCI Information Systems Inc.
[EMAIL PROTECTED]
618-622-4145
i was at an oracle group meeting and one of the RAC specialists at oracle was talking.
he said that that kind of thing 'can' be done, but is incredibly expensive. you need
redundancy and fail safes like crazy.
any time you do an upgrade, bad things may happen.
From: Tracy Rahmlow [EMAIL
Tracy, both OPS (8i) and RAC (9i)support independent node shutdown.
Both support listener based load balancing so that incoming connections
will be evenly spread on all nodes. That still doesn't give you the true
24 x 7 x 365 availability. For that, you need two replicated copies of the
database,
Hi,
Unfortunately I'm gonig to add the negative view, like several others
have...
True 24x7x365 (good pick-up Pete on the 7 year thing) will be limited by
much more than database and operating system availability. We just did a
major software upgrade last weekend and part of the upgrade
True
24x365 is just about impossible. No if, ands. or buts about it. Why
is because of the number of factors outside your control that affect system
availability. Sure your web sever and database are up 24x365, but your ISP
has 1 hour down time each month for maintenance. OOPS!! from a
When you want true 24x7 without compromises, then you have to step closer to
the client anyway.
This means, you have two databases for example and your app server
multiplexes all transactions to both ones.
This should be faster than sync standby or sync replication, because app
server can send
Title: Re: 24 x 7 x 365
As I mentioned a few minutes ago in another thread, there is an application using Oracle Rdb on an HP OpenVMS cluster located at HP in Colorado Springs that has been up and available continuously for the past 11-12 years.
on 12/10/03 2:49 PM, Goulet, Dick at [EMAIL
17 matches
Mail list logo
