Re: Compare logical standby database with Advanced Replication

as someone who's implemented both, I would suggest standby database for your high availability option as opposed to replication. Let's just say that even the Oracle instructors in the replication class were saying that replication requires lots of hand holding. Or let me rephrase what my instructor said: "if you're going to do replication, you need a full time DBA dedicated to replication and nothing else." After playing with it myself, I would have to agree.

Standby on the other hand is immensely easier and requires very little, if any, hand holding. Once you get it set up, it virtually maintains itself (provided you don't add lots and lots of datafiles on the primary site on a regular basis). Anyway, yeah, go with standby as there are lots of documentation on metalink supporting this concept.

wangbin wrote:

> Hi
>
> Oracle 9.2 RAC on redhat AS is used for our OLTP database. We need to
> find out a way to replicate data from OLTP database to report server
> for reporting. There are two solutions that we consider at the moment.
> One is logical standby database, and the other is Advanced
> Replication. The following is questions we have regarding this issue.
>
> 1. In logical standby database, are you able to create new objects,
> such as summary tables, and store data from resource other than the
> primary database?
> In the other word, part of the database is sync from primary database,
> like
> what happen in replication.
>
> 2. How to compare logical standby database with Advanced Replication,
> in terms of performance overhead to primary database, complexity of
> maintainance, and reliability?
>
> The following is the information I collect.
> Advanced Replication:
> Significant extra load on the production database for maintaining and
> propagating the replicated data. For example, the load on the
> production is high when you have to refresh the whole table after the
> report server is down for some reason.
>
> Logical standby database:
> Some extra load, such as redo needs primary key be included, on
> production database maintaining logical standby database
> functionality.
> New functionality to Oracle 9.2, which means we need to check its
> reliability.
> Data Guard Broker is not availible for RAC, which increase the
> difficulty for support.
>
> I try to assess and compare administrative/support burden for each
> option.
>
> Thanks,
> Bin

--
Phillip

Meetings:  None of us is as dumb as all of us.