Running a Log Gap Report

Owned by Anton Els (Unlicensed)
Jan 10, 2014
1 min read

A log gap report is important it can quickly provide you with an overview if your standby database is up to date and if not how far behind it is.

The command used to run the log gap report should be executed from the primary database. The log gap report can be generated by running:

dbvisit -i <DDC>

 

Below is an example of a log gap report indicating that the standby still need to apply one archive log:

oracle@dbvlin501[/usr/dbvisit/standby]: ./dbvisit -i proddb
=============================================================
Dbvisit Standby Database Technology (7.0.01.11254) (pid 10977)
dbvisit started on dbvlin501: Thu Aug 22 23:25:09 2013 ()
=============================================================

Dbvisit Standby log gap report for proddb at 201308222325:
-------------------------------------------------------------
Standby database on dbvlin502 is at sequence: 5439.
Primary database on dbvlin501 is at log sequence: 5441.
Primary database on dbvlin501 is at archived log sequence: 5440.
Dbvisit Standby last transfer log sequence: 5440.
Dbvisit Standby last transfer at: 201308222320.

Archive log gap for proddb:  1.
Transfer log gap for proddb: 0.
Standby database time lag (HH:MI:SS): 00:13:07.
    No Mail sent as SEND_MAIL_FLAG = N

=============================================================
dbvisit ended on dbvlin501: Thu Aug 22 23:25:12 2013
=============================================================