To ensure the primary and standby databases are up to date, you can run the Log Gap Report using the following command from the primary database server:
./dbvctl -d <DDC> -i |
Important: In the example below the line numbers indicated below on the left with "1. -->", "2. -->" etc is used only for documentation purpose to help explain the report and is not included in the actual report
[oracle@dbv1 standby]$ ./dbvctl -d DEV -i ============================================================= Dbvisit Standby Database Technology (9.0.0_1271_g4b00fb49) (pid 1156) dbvctl started on dbv1: Thu May 9 11:58:15 2019 ============================================================= Dbvisit Standby log gap report for DEV at 201905091158: ------------------------------------------------------------- Description | SCN | Timestamp ------------------------------------------------------------- 1. -->Source 1127912 2019-05-09:11:58:16 +12:00 2. -->Destination 1127815 2019-05-09:11:54:35 +12:00 3. -->Standby database time lag (DAYS-HH:MI:SS): +00:03:41 Report for Thread 1 ------------------- SOURCE 4. -->Current Sequence 14 5. -->Last Archived Sequence 13 6. -->Last Transferred Sequence 10 7. -->Last Transferred Timestamp 2019-05-09 11:54:44 DESTINATION 8. -->Recovery Sequence 11 9. -->Transfer Log Gap 3 10. -->Apply Log Gap 3 ============================================================= dbvctl ended on dbv1: Thu May 9 11:58:17 2019 ============================================================= |
The report line numbers are explained in more detail below:
The log gap report is much more detailed in Dbvisit Standby Version 9, the log gap report is divided into three parts.
The First part being the table where it provides information
The second part of the log gap report provides information about the source/primary database
The third part of the log gap report provided information about the destination/standby database
To ensure the primary and standby databases are up to date, you can run the Log Gap Report using the following command from the primary database server:
./dbvctl -d <DDC> -i |
Below is an example of running a Log Gap report in a Single Instance Primary environment.
Information for only one thread will be shown.
[oracle@dbv1 standby]$ ./dbvctl -d DEV -i ============================================================= Dbvisit Standby Database Technology (9.0.0_1271_g4b00fb49) (pid 1325) dbvctl started on dbv1: Thu May 9 12:20:19 2019 ============================================================= Dbvisit Standby log gap report for DEV at 201905091220: ------------------------------------------------------------- Description | SCN | Timestamp ------------------------------------------------------------- Source 1128991 2019-05-09:12:20:18 +12:00 Destination 1127908 2019-05-09:11:58:02 +12:00 Standby database time lag (DAYS-HH:MI:SS): +00:22:16 Report for Thread 1 ------------------- SOURCE Current Sequence 14 Last Archived Sequence 13 Last Transferred Sequence 13 Last Transferred Timestamp 2019-05-09 12:19:46 DESTINATION Recovery Sequence 14 Transfer Log Gap 0 Apply Log Gap 0 ============================================================= dbvctl ended on dbv1: Thu May 9 12:20:22 2019 ============================================================= |
Running the log gap report in an Oracle RAC environment will list information about all the threads in the Oracle RAC cluster.
The command to be executed is the same, but the result as you can see below will include information for all threads.
oracle@kiwi81[/acfs/dbvisit/standby]: ./dbvctl -d MYDEV -i ============================================================= Dbvisit Standby Database Technology (9.0.0_1383_g276092d5) (pid 27344) dbvctl started on kiwi812-vip: Fri May 24 13:15:58 2019 ============================================================= Dbvisit Standby log gap report for MYDEV at 201905241315: ------------------------------------------------------------- Description | SCN | Timestamp ------------------------------------------------------------- Source 1115263 2019-05-24:13:16:50 +12:00 Destination 1115055 2019-05-24:13:12:50 +12:00 Standby database time lag (DAYS-HH:MI:SS): +00:04:00 Report for Thread 1 ------------------- SOURCE Current Sequence 13 Last Archived Sequence 12 Last Transferred Sequence 12 Last Transferred Timestamp 2019-05-24 13:13:16 DESTINATION Recovery Sequence 12 Transfer Log Gap 0 Apply Log Gap 1 Report for Thread 2 ------------------- SOURCE Current Sequence 5 Last Archived Sequence 4 Last Transferred Sequence 4 Last Transferred Timestamp 2019-05-24 13:13:30 DESTINATION Recovery Sequence 5 Transfer Log Gap 0 Apply Log Gap 0 ============================================================= dbvctl ended on kiwi812-vip: Fri May 24 13:17:24 2019 ============================================================= |
This section provides you with an overview of how you can run the Log Gap Report using the Central Console (GUI).
Step 1: Navigate to the Database Actions Menu option as shown below [1]
Step 2: For the DDC in question (DEV in this example), click on the first icon highlighted (two pages on top of each other) as shown below [1]. The [ 2] shows the precise time gap between source and destination. This will start the log gap report process.
Step 3: Review the log gap report as shown below.
To reduce the Time, Transfer or Archive Log gap, you need to enable the shipping and applying of logs
From Dbvisit standby 9.0.14, there are new improvements in task actions, statuses and flexibility. Below are the changes
All active tasks now come with a terminate task button. When you press this button on any active task, it would kill the task.