Streams Apply applies transactions sequentialy when objects do not exists on target site
(Doc ID 1124823.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124.0 [Release 9.2 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
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.
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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!