Once the replication process has started the Dbvisit Replicate command console can be used to monitor the replication and to find the current status.
Start the Dbvisit Replication command console with the generated script:

start-console.sh

On Windows the script will be: start-console.bat

The Dbvisit Replication command console can also be started using the dbvrep executable with the correct DDC file:

dbvrep --ddcfile w112a.ddc

In this example, w112a.ddc is the name of the DDC file.

See Dbvisit Replication command console for more information on how to start the Dbvisit Replicate command console.

The Dbvisit Replication command console shows the running processes:

-MINE IS running. Currently at redo log sequence 229 and SCN 4794116.
APPLY IS running. Currently at redo log sequence 229 and SCN 4794115 (17/01/2014 14:34:56).
Dbvisit Replicate 
Copyright (C) Dbvisit Software Limited. All rights reserved.
DDC file w112a.ddc loaded. 
Try "help"
dbvrep>

*Where w112a.ddc is an example name of a DDC file.

The top part of the Dbvisit Replicate command console displays the current status of all the replication processes in real time and displays the current SCN (Oracle system change number) of both the source and target databases.

Showing the replication progress for tables

The replication progress for tables can be shown in the Dbvisit Replicate command console:

dbvrep> list progress
Progress of replication: total/this execution
------------------------------------------------------------------------------------
SCOTT.AVI_OBJECTS: 100% Mine:20/20 Unrecov:0/0 Applied:20/20 Conflicts:0/0
------------------------------------------------------------------------------------
1 tables listed.

See Dbvisit Replication command console for more information on how to start the Dbvisit Replicate command console.

To include the internal replication of the Dbvisit Replicate tables:

dbvrep> list progress all

The list progress can also be shown in real time as part of the status bar by setting in the DDC file (this is on by default):

dbvrep> set STATUS_BAR status+list

If the number of tables is too large to display in the list progress, then this can be limited to active tables only:

dbvrep> set STATUS_BAR_ACTIVE_TABLES 10

The Dbvisit Replicate console has to be restarted for some of these setting to take affect.

The list progress tables displays the following information for each object that is replicated:

• Replication in %: 100% means that all data has been replicated.
• MINE: Counts the number of data rows that have been mined in total and for this execution. This number will always increase and will not decrease for delete statements.
• Unrecov: Counts the number of changes (blocks or block ranges) that cannot be replicated due to nologging (also known as unrecoverable) operations in total and for this execution.
• Applied: Counts the number of data rows that have been applied in total and for this execution. This number will always increase and will not decrease for delete statements.
• Conflict: Counts the number of data rows that are in conflict in total and for this execution.
• Last: The last time that replication of data occurred and status (OK or short error description, e.g. ORA error)

Showing the replication progress for PL/SQL

The replication progress for PL/SQL can be shown in the Dbvisit Replicate command console:

dbvrep> list progress plsql
List of last 10 PLSQL DDL commands. See DBRSAPPLY_DDL_HISTORY on target for full list.
----------------------------------------------------------------------------------------
  23			   SCOTT.P17		   CREATE PROCEDURE  23.01.2012 12:10:26
  22			   SCOTT.P16		    ALTER PROCEDURE  23.01.2012 12:10:26
  21			   SCOTT.P17		   CREATE PROCEDURE  23.01.2012 12:10:26
   1			   SCOTT.P16		   CREATE PROCEDURE  23.01.2012 03:20:37

The limit of 10 is configurable with _PLSQL_PROGRESS_LIMIT.