Re: Oracle Streams - Avoiding Delete statement.

Well how to you define purge. If you say delete it's delete that will not
consider anything else.

So, there are ways to totally avoid delete. But in your case you might need
to create different table and move data to that table when purge occurs and
then delete those data on target db. But, if this is bi-directional
replication then you might have to try setting up manual replication for
that particular table. You can try using triggers and pass flag saying this
is purge activity and based on that might need to apply some kind of logic
to accomplish this.

This are just thought based on what i understand. But it depends on your
environment and requirements.

On Tue, Nov 30, 2010 at 8:53 AM, Prabhu Krishnaswamy <
prabhu_adam@xxxxxxxxxxx> wrote:

>  Lists,
>
> We are setting up the streams for our critical application.  The app. team
> has got a requirement, which should purge a data on the master database but
> those should not be repliacated to the target database. The purge data
> happens from time-to-time on Master DB but this should not purge data on
> Replicated DB. After Streams setup, is there a way to disable replication
> during these scheduled purges? Replicated DB also serves as archive for
> Master DB.
>
> After Streams is setup is there a way to avoid these purges applied to
> replicated DB.
>
> Not all the delete of the table should be avoided, only the purge activity
> based on the retention should be avoided.
>
>
> Thanks,
> Prabhu
>
>



-- 
Thanks & Regards,
Taral Desai

Other related posts: