Re: Duplicating a database AND maintaining it

From: Donkey Hot <spam_at_plc.is-a-geek.com>
Date: 26 Sep 2007 16:19:58 GMT
Message-ID: <Xns99B7C6A2918ASH15SGybs1ysmajw54s5@194.100.2.89>

"fitzjarrell_at_cox.net" <fitzjarrell_at_cox.net> wrote in news:1190823104.838187.315730_at_g4g2000hsf.googlegroups.com:

>
> You could implement Streams between DB and DB1; this would replicate
> the data from databases on DB to those on DB1 and not clutter the DB1
> environment with additional archivelogs as they would be 'mined' on
> the source server. Presumng you have no 'offending' data types in the
> databases this could work nicely to 'pump' transactions from DB to
> DB1, while the physical Data Guard configuration writes the
> archivelogs to DB2 for application, keeping everything 'in synch'.
>
>
> David Fitzjarrell
>
>

Thanks, will have a look on Streams, which I do not know. I have no knowledge about the database contents, so I don't know about possible 'offending' data types, and what types those might be. Something to study.

Thanks! Received on Wed Sep 26 2007 - 11:19:58 CDT