Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 E-mail Us
 Oracle Articles
New Oracle Articles

 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog

 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Oracle Support

 SQL Tuning

 Oracle UNIX
 Oracle Linux
 Remote s
 Remote plans
 Application Server

 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S


 Consulting Staff
 Consulting Prices
 Help Wanted!


 Oracle Posters
 Oracle Books

 Oracle Scripts

Don Burleson Blog 







Monitoring the Data Guard Log apply service

Oracle Database Tips by Donald BurlesonDecember 9, 2015


Monitoring Data Guard Log Apply Services

The v$logstdby and v$logstdby_stats views provide comprehensive data about the various processes involved in the SQL Apply operations. As mentioned earlier in the "Data Guard Architecture" chapter, the SQL Apply operation is facilitated by LogMiner technology.

The v$logstdby view can be queried to find the state of the individual process of LogMiner. The following simple query on v$logstdby will give sufficient information needed to analyze any problem with the log apply service:


Oracle Data Guard

Monitoring Log Apply Services

Order by

The following is a sample output, from the above query showing the status of the log apply service:

PID    TYPE         STATUS
------ --------     -------------------------------------
1479   ANALYZER     ORA-16116: no work available
1475   BUILDER      ORA-16127: stalled waiting for additional
                    transactions to be applied
1477   PREPARER     ORA-16116: no work available
1471   COORDINATOR  ORA-16116: no work available
1473   READER       ORA-16127: stalled waiting for additional
                    transactions to be applied
1481   APPLIER      ORA-16116: no work available

Monitoring Log Apply Services

The v$logstdby_stats view contains the performance statistics on the log apply service. The records from this view will be cleared when the log apply service is not running. The following query can be used for performance monitoring purposes:


The output from the v$logstdby_stats view is as follows:

NAME                                   VALUE
-----                              ---------
number of preparers                  1
number of appliers                   1
maximum SGA for LCR cache            2
parallel servers in use              5
maximum events recorded            100
transaction consistency            FULL
record skip errors                   Y
record skip DDL                      Y
record applied DDL                   Y

NAME                                   VALUE
-----                              ---------
coordinator state                                          APPLYING
transactions ready                                                         2
transactions applied                                                      2
coordinator uptime                                                       4
preparer memory alloc waits                                         2
builder memory alloc waits                                      2346
attempts to handle low memory                               2346
successful low memory recovery                                    1
pageout avoided                                                           0
pageout avoided by rollback                                         0
pageouts                                                                       0
memory low watermark reached                                   0
recovery checkpoints not taken                                     0
recovery checkpoints taken                                           0
available work units                                                  155
prepared work units                                                      0
committed txns ready                                                    0
un-committed txns ready                                               0
committed txns being applied                                         0
un-committed txns being applied                                    0

Monitoring Log Apply Services

Column Thread      format 99
Column Status_Code format a10

   l.FILE_NAME Archive_Log_Name,
   l.THREAD# Thread,
e.STATUS_CODE Status_Code

The above text is an excerpt from the book: Oracle Data Guard Handbook

Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster


Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


Copyright © 1996 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.