Dinesh Have you considered a multi-master replication solution? You could = easily setup a read-only role for users of db02. Given that only one of = the databases is being maintained you wouldn't get any data conflicts = and hence not need any special conflict resolution strategies or delete = logic or special GUID generators. You could easily partition sequences = with odd on db01 and evens on db02. The only down side is that you'll = have issues if you have LONGs in the schema. Have you considered what happens after disaster recovery. I assume you = will want to re-setup db01 as your READ-ONLY DR backup? With a = multi-master solution you can "relatively" easily create a secondary = master site as everything is a master, there are no snapshots Regards Peter Miller -----Original Message----- From: Seema Singh [mailto:oracledbam@xxxxxxxxxxx] Sent: 30 June 2004 05:12 To: oracle-l@xxxxxxxxxxxxx Subject: RE: REPLICATION stephen, But this option is not going to work with rowid .It is not possible to=20 create the snapshot as rowid, an error ORA-12058 will be raised in case = you=20 try to create the snapshot as rowid.i have tested these option. thanks >From: Stephen.Lee@xxxxxxxx >Reply-To: oracle-l@xxxxxxxxxxxxx >To: oracle-l@xxxxxxxxxxxxx >Subject: RE: REPLICATION >Date: Tue, 29 Jun 2004 16:34:14 -0500 > > > -----Original Message----- > > because when we run create snapshot command it will failed > > with error object already exist.? > >I don't know your Oracle version, but if you can: > >create snapshot xyz ON PREBUILT TABLE etc. ... > >Then your Oracle version is OK. > >There is more than one way to create the tables in the secondary = database. >I usually create the empty tables, then for each table: > >exec dbms_snapshot.refresh('TABLE_NAME','C') > >set up the refresh group and refresh schedule (usually every five = minutes >for me). > >This certainly isn't the only way to do it. > >I have never set up a failover site like this. I just do it this way >because we have so many frequent changes, that I do not want to = completely >lose a snapshot table whenever I must temporarily drop a snapshot in = order >to make some change. Sometimes in our test environment, we might want = to >split a replication pair to run independently for a while. Then put >replication back in later. > >---------------------------------------------------------------- >Please see the official ORACLE-L FAQ: http://www.orafaq.com >---------------------------------------------------------------- >To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx >put 'unsubscribe' in the subject line. >-- >Archives are at //www.freelists.org/archives/oracle-l/ >FAQ is at //www.freelists.org/help/fom-serve/cache/1.html >----------------------------------------------------------------- _________________________________________________________________ Watch the online reality show Mixed Messages with a friend and enter to = win=20 a trip to NY=20 http://www.msnmessenger-download.click-url.com/go/onm00200497ave/direct/0= 1/ ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html ----------------------------------------------------------------- ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------