Re: shared database sequence.

Actually, one of my CT is doing this in a high transaction volume HA solution.
No Data Guard (no RAC!), simply balance the load at two production servers, sitting at 20m distance.
They asynchronously forward the transactions to the 'other' server. If one server is lost, the other can deal with the load. Switching the user-apps to another server is split-second work. The amount of transactions that can get lost costs less (in the meaning of USD) than an expensive RAC/DG and what have you solution. Perfect business case, perfect solution. Truly HA by design. I like it.

Best regards,

Carel-Jan Engel

===
If you think education is expensive, try ignorance. (Derek Bok) ===

On Mon, 2007-02-26 at 23:05 +0300, Syed Jaffar Hussain wrote:

> Thanks for all your suggestions.
>
> I guess having separate sequences with odd and event sequence numbers
> would going to work.
> The scenario is like to have two databases one at local site and
> another at remote site (not at far distance) and replicate the
> information or sync the data between two databases actively. Its very
> highly OLTP with more than 400 transaction per second. Therefore,
> synonym or getting nexval through dblink would probably is not
> acceptable.
>
> Regards
>
> Jaffar
>
>
> On 2/26/07, EPS - DBA (Group) <dbamail_at_police.edmonton.ab.ca> wrote:
>
> Would this work?
>
> A really simple, not so elegant solution would be to
> have a sequence generator on each database
>
> DB#1 start with 1 increment by 2 (generates only odd
> sequence numbers)
> DB#2 start with 2 increment by 2 (generates only even
> sequence numbers)
>
>
>
>
>
>
> ______________________________________________
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org] On
> Behalf Of Mark W. Farnham
> Sent: Monday, February 26, 2007 10:47 AM
> To: sjaffarhussain_at_gmail.com; 'oracle-l'
> Subject: RE: shared database sequence.
>
>
> Do you just need uniqueness or do you need
> some correspondence amongst the databases?
>
>
>
> If so, how chunky can the correspondence be?
>
>
>
> If the database servers are reliably near each
> other in a network latency sense you would
> still have to decide whether the network
> latency of using a dblink to get sequence
> numbers from a different database is
> acceptable.
>
>
>
> If you don't need a correspondence, then you
> can maintain uniqueness by assigning something
> like a database number to each database and
> tacking a suffix on, so for example all the
> ids from database 3 end in 3.
>
>
>
> mwf
>
>
>
>
>
> ______________________________________________
>
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org] On
> Behalf Of Syed Jaffar Hussain
> Sent: Monday, February 26, 2007 4:14 AM
> To: oracle-l
> Subject: shared database sequence.
>
>
>
>
>
>
> Hello List,
>
>
>
>
>
> Is it possible to share a database sequence
> between multiple databases? Not in RAC of
> course.
>
>
> We are planning to have two databses
> exchanging information (replicating) using
> third party solution. But, stuck with the
> issues of sequences.
>
>
>
>
>
> Thanks
> --
> Best Regards,
> Syed Jaffar Hussain
> Oracle ACE
> 8i,9i & 10g OCP DBA
>
> http://jaffardba.blogspot.com/
> http://www.oracle.com/technology/community/oracle_ace/ace1.html#hussain
> ----------------------------------------------------------------------------------
> "Winners don't do different things. They do
> things differently."
>
>
>
>
>
>
> --
> Best Regards,
> Syed Jaffar Hussain
> Oracle ACE
> 8i,9i & 10g OCP DBA
>
> http://jaffardba.blogspot.com/
> http://www.oracle.com/technology/community/oracle_ace/ace1.html#hussain
> ----------------------------------------------------------------------------------
> "Winners don't do different things. They do things differently."

--
http://www.freelists.org/webpage/oracle-l