Re: Help required on Data Guard

Hi Yang,

Thank You Very much for your response.

> 1. for data synchronization, you need to use data replication. that's right.
> juste be carefull that there is a little difference between the 2 databases
> : one is designed as super-master and the other master. this is important
> when you get to restore.

In our case, both the databases will be same in both the locatinons. loc1_db is the master for loc2_db and loc2_db is the master for loc1_db. So that both database will be in sync. This replication can done for transaction basis? will there be any performance issues? Because, for each transaction it should go to remote location and update the transaction. Or updation of the remote site on some frequent intervals will fine?

> 2. for standby and backup databases :
> the standby database means some downtime when to restore, because you need
> 'transforming' your standby database to a normal production database.
> if you design your system to a 'no-downtime' system when disaster occurs,
> you should consider rac, which means you should have at least 2 db-servers
> in each location.

As of now, the admins are creating application clusters using JBOSS for swithcover/failover cases, like if there is any problem with primary database, then the application request should go to Standby Database. In that case, do have to shutdown stand by database and make as primary(means, manual intervention)?

is there any document or link which give steps to configure and test the DataGuard?

Thanks,
Praveen

"Yang" <dbaoracle_at_wanadoo.fr> wrote in message news:<419f7e16$0$14316$626a14ce_at_news.free.fr>...
> Hi Praveen,
>
> 1. for data synchronization, you need to use data replication. that's right.
> juste be carefull that there is a little difference between the 2 databases
> : one is designed as super-master and the other master. this is important
> when you get to restore.
>
> 2. for standby and backup databases :
> the standby database means some downtime when to restore, because you need
> 'transforming' your standby database to a normal production database.
> if you design your system to a 'no-downtime' system when disaster occurs,
> you should consider rac, which means you should have at least 2 db-servers
> in each location.
>
> hth.
>
> Yang
> dba oracle.
>
>
> "Praveen" <spraveen2001_at_yahoo.com> a écrit dans le message de news:
> 98d8ec76.0411200150.2d205e15_at_posting.google.com...
> > Hi All,
> >
> > We are developing an application using Java and Oracle 10g(Backend).
> > It is a billing application. We need to deploy the application in 2
> > different locations/places. Now, there is a requirement of Data
> > synchronization between 2 location(The moment, a record is added in
> > any of the location, the should get reflected in another location and
> > vice-versa). For Eg: The database in loc1 has to synchronized with
> > loc2 and vice-versa. In addition to this, in each location, they want
> > standby database and backup databases. Means, there should not be any
> > downtime in any of the locations.
> >
> > For the above situation, can i go with the following options:
> >
> > 1. For Data Synchronization between 2 locations: Oracle 10g Data
> > Replication?
> >
> > 2. For creating StandBy and Backup Databases: Oracle 10g Data Guard.
> >
> > I think i need not to use Oracle 10G RAC for this, is that correct?
> >
> > Please suggest me how i can approach to this situation.
> >
> > Thanks,
> > Praveen
Received on Mon Nov 22 2004 - 03:47:54 CST