Streams Apply applies transactions sequentialy when objects do not exists on target site (Doc ID 1124823.1)

Last updated on AUGUST 30, 2021

Applies to:

Symptoms

Latency on your Streams environment is growing and you have observed that your apply servers are applying sequentially though apply parallelism has been set. When checking v$streams_apply_server, only one process is on EXECUTE TRANSACTION state, meanwhile others are waiting on 'WAIT DEPENDENCY'



Note that the processes on WAIT DEPENDENCY state are waiting for transaction id 0.0.0.

Changes

It is not expected dependency between the transactions.

The streams processes have a transformation defined because not all the objects (schemas) existing in source site do exists on <target site.

The size of transactions is not big (=< 999 lcrs/tx).
Remember that when apply have to manage transactions with more than 999 lcrs/tx it forces to apply sequentially, although dependent transaction is not 0.0.0.

Cause