My Oracle Support Banner

[Bug 26676850] Sql Apply Lagging Due To Significant Dependency Waits (Doc ID 2359146.1)

Last updated on APRIL 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.


SQL Apply is lagging behind for the last few days. Throughput seems to be reduced due to high amount of dependency waits.

  SQL> col event format a50 trunc
  SQL> select ls.status_code, s.event, count(1) No_Of_Appliers
  2 from v$logstdby ls
  3 , v$streams_apply_server sas
  4 , v$session s
  5 where ls.type = 'APPLIER'
  6 and ls.status_code in ( 16124, 16123 )
  7 and ls.logstdby_id = sas.server_id
  8 and s.sid = sas.sid
  9 group by ls.status_code, s.event;

  ----------- -------------------------------------------------- --------------
  16124 Streams apply: waiting for dependency 8

Description of ORA-16124:

  ORA-16124 'transaction %s %s %s is waiting on another transaction'

In awr_report_47534_47546.html in awr_report_47534_47546.html, we see background wait 'Steams apply: waiting for dependency' has average wait of 57ms over the 12 hours captured in the report.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.