Skipping transaction for batch job on streams

Question

We need to run a batch job on streams soruce side. I would like to skip this transaction from streams to capture & apply.
Then run the batch jobs on source & target seperately. How to do it?

Answer 1

There are plenty of valid reasons to execute a batch job independently of replication, not the least of which is that it's a recommended best practice from Oracle.
Minimize the Performance Impact of Batch Processing
For best performance, the commit point for a batch processing job should be kept low. Also, if a large batch processing job must be run at a source database, then consider running it at each Streams replication database independently. If this technique is used, then make sure the changes resulting from the batch processing job are not replicated. To accomplish this, run the DBMS_STREAMS.SET_TAG procedure in the session that runs the batch processing job, and set the session tag to a value that will not be captured by a capture process.
Unless you have made explicit changes to the tag used in your streams rules they are all configured to only replicate if the streams tag is null. If you set this to not-null in a session, changes within that session will not be replicated. For example
exec dbms_streams.set_tag(hextoraw('99'));
You can turn it back on in that session (if needed) with
exec dbms_streams.set_tag(null);
So, if you set the tag in your batch job you can execute it independently of replication.