Hi I haven't used it myself, but just before you do the delete, use DBMS_STREAMS.SET_TAG to mark all the following redo entries in the session with some specific tag value. An then modify streams capture process to filter out all the messages with that tag. Ilmar On Tue, Nov 30, 2010 at 4:53 PM, 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. -- Ilmar Kerm -- //www.freelists.org/webpage/oracle-l