Page Comparison

Dbvisit Standby can inspect the primary and standby databases and report on the latest log sequence numbers. It includes reporting on the:

...

 dbvisit -i w102n 
 ============================================================= 
 Dbvisit Standby Database Technology 
 dbvisit.exe started on win2003se-01 
 ============================================================= 

 Contacting Standby Database w102n on win2003se-02... 
 Last standby sequence obtained (26). 

 Dbvisit report: 
 ------------------------------- 
 Standby database on win2003se-02 is at sequence: 26 
 Primary database on win2003se-01 is at log sequence: 29 
 Primary database on win2003se-01 is at archived log sequence: 28 
 Dbvisit last transfer log sequence: 28 

 Archive log gap: 2 
 Transfer log gap: 0 
 ============================================================= 
 dbvisit.exe ended on win2003se-01 
 =============================================================

Where w102n is the name of the database.

_{Image Modified}Home > Run > Run Interactive > Primary Server tab > select Database from drop-down menu > select Default from Run Action drop-down menu > Run

The log sequence number from the primary database will always be one or more sequences ahead of the last log sequence that Dbvisit Standby will have transferred. This is because the log sequence shown for the primary database is the latest log sequence that is not archived yet (redo log).
This reporting is non-intrusive. No log switches are performed and no logs are transferred. 
When this command is run, the information is also inserted into the Dbvisit Standby database repository (DDR) table called dbv_sequence_log. This table can be used for log gap analysis over time. 
Note: The standby database must be available in standby mode or in READ ONLY mode when this command is executed. If the standby database is not available, Dbvisit Standby will automatically start the standby database if AUTO_START_STANDBY_DB=Yes.

...