1 Reply Latest reply on May 15, 2008 7:44 PM by JustinCave

    What is preferred geo-redundant Oracle architecture?

    ALU Steve
      All,

      We are looking at setting up a trans-continental, geo-redundant Oracle RAC system in an active/active type setup with the caveat that during sunny day operations, west coast ops will be handled by the west cluster and east coast ops will be handled by the east cluster.

      During normal operations, west coast cluster needs to replicate changes to east and vice versa so that in the event of say a west coast outtage, all traffic would be sent to east coast and handled appropriately until west coast can resume.

      What are the best methods for architecting such a system? DataGuard? Streams?

      Thanks in advance!
        • 1. Re: What is preferred geo-redundant Oracle architecture?
          JustinCave
          If both clusters are going to be generating changes (rather than one cluster being used as a reporting instance), you probably don't want to be using DataGuard (at least not for this-- you may well want to use DataGuard for other reasons). The two options for multi-master replication would be Streams and Advanced Replication. Of the two, assuming recent versions of Oracle and that you're using data types that are compatible with Streams, Streams is the preferred technology. Streams was designed as the successor to Advanced Replication and solves a lot of the problems associated with old-school replication. Of course, that also means that it's a newer technology, so there are fewer people out there with a lot of experience with it, and you're a bit more likely to encounter odd errors or configuration issues during development (particularly if you still have 9.2 databases).

          Of course, I would make absolutely sure that you really need two different databases in two different data centers. If you could consolidate to one data center (with the other data center providing fail-over and some read-only caches based off the standby), that is generally going to simplify the architecture of the application.

          Justin