06 - View the Replication

Owned by Arjen Visser
Last updated: Sept 24, 2014

As soon as SwingBench starts generating DML changes, the tables that have changes applied to them will appear in the Replication Console.

See the TIPS below for handy common Dbvisit Replicate tips.

The replication can be viewed from the Dbvisit Replication console. 

1. Switch to the session where the Dbvisit Replicate console is running and the replication can be seen to be progressing while Swingbench is running in the background. 

/ Dbvisit Replicate 2.7.06(MAX edition) - Evaluation License expires in 30 days
MINE IS running. Currently at plog 26 and SCN 527369 (08/12/2014 15:54:09).
APPLY IS running. Currently at plog 26 and SCN 527392 (08/12/2014 15:54:10).
Progress of replication dbvrep_XE:MINE->APPLY: total/this execution
--------------------------------------------------------------------------------------------------------------------------
REPOE.CUSTOMERS:     98%  Mine:56/56     Unrecov:0/0   Applied:55/55       Conflicts:0/0       Last:12/08/2014 15:54:11/OK
REPOE.ADDRESSES:    100%  Mine:55/55     Unrecov:0/0   Applied:55/55       Conflicts:0/0       Last:12/08/2014 15:54:11/OK
REPOE.CARD_DETAILS: 100%  Mine:47/47     Unrecov:0/0   Applied:47/47       Conflicts:0/0       Last:12/08/2014 15:54:11/OK
REPOE.ORDER_ITEMS:   95%  Mine:235/235   Unrecov:0/0   Applied:224/224     Conflicts:0/0       Last:12/08/2014 15:54:11/OK
REPOE.ORDERS:        93%  Mine:195/195   Unrecov:0/0   Applied:182/182     Conflicts:0/0       Last:12/08/2014 15:54:11/OK
REPOE.INVENTORIES:   95%  Mine:228/228   Unrecov:0/0   Applied:217/217     Conflicts:0/0       Last:12/08/2014 15:54:11/OK
REPOE.LOGON:         97%  Mine:265/265   Unrecov:0/0   Applied:259/259     Conflicts:0/0       Last:12/08/2014 15:54:11/OK
--------------------------------------------------------------------------------------------------------------------------
7 tables listed.
dbvrep>

In the above output of the Replication Console the line numbers are shown for reference and each line number relates to the following explanation:

  1. Shows the version number, edition of the software (LTD, XTD, or MAX), and the type of license. 
  2. Shows the MINE process is running. Which PLOG sequence (which is the same as the redo log sequence) and SCN the MINE is processing and the database time related to the SCN
  3. Shows the APPLY process is running. Which PLOG sequence and SCN the APPLY is processing and the (source) database time related to the SCN
  4. Name of the replication
  5. Separator
  6. Replication statistics for table REPOE.CUSTOMER. The replication is at 98%. 56 records have been mined. 55 records have been applied. There are 0 conflicts.
  7. Replication statistics for table REPOE.ADDRESSES. The replication is at 100%. 55 records have been mined. 55 records have been applied. There are 0 conflicts.
  8. Replication statistics for table REPOE.CARD_DETAILS. The replication is at 100%. 47 records have been mined. 47 records have been applied. There are 0 conflicts.
  9. Replication statistics for table REPOE.ORDER_ITEMS. The replication is at 95%. 235 records have been mined. 224 records have been applied. There are 0 conflicts.
  10. Replication statistics for table REPOE.ORDERS. The replication is at 93%. 195 records have been mined. 182 records have been applied. There are 0 conflicts.
  11. Replication statistics for table REPOE.INVENTORIES. The replication is at 95%. 228 records have been mined. 217 records have been applied. There are 0 conflicts.
  12. Replication statistics for table REPOE.LOGON. The replication is at 97%. 265 records have been mined. 259 records have been applied. There are 0 conflicts.
  13. Separator
  14. Number of tables listed in the command console. 
  15. The Replication Console command prompt.

TIP 1

If the Dbvisit Replicate console is not running then:

  1. Connect to the souce server as oracle.

  2. Cd to the correct directory.

    cd ~oracle/dbvrep_XE

  3. Start the Replication console:

    ./start-console.sh

  4. The console can also be started on the target server *. The manual command to start the console is: 

    dbvrep --ddcfile /u01/app/oracle/dbvrep_XE/dbvrep_XE-APPLY.ddc

    * The console can be started on any server that has a TNS connection to both the source and target database, and has the Dbvisit Replicate software installed (including Windows or the host machine). You will need to copy either the MINE ddc or APPLY ddc file to the server you are running the console from. This is to connect the console to the replication.

TIP 2

If there are many tables in the replication, then only a certain number of tables will be shown in the console.

The number of active tables shown in the console is configurable with setting STATUS_BAR_ACTIVE_TABLES.

To get a list of all the tables in the replication, use the command:

dbvrep> list progress

The list progress report can be emailed automatically if notification is setup. The schedule when this report is sent is controlled by NOTIFY_DAILY_LIST_PROGRESS_TIME24

TIP 3

The statistics of the replication can be viewed with the following commands:

dbvrep> list stats
dbvrep> list stats all
dbvrep> list stats REPOE.ORDER_ITEMS

TIP 4

There are many settings and configurations possible with Dbvisit Replicate. To see all the settings type: show all

For example, to see all the settings regarding notifications:

dbvrep> show notify                                                                                                                          
*.NOTIFY_ALERT_EMAIL = OFF
*.NOTIFY_ALL_EMAIL = OFF
*.NOTIFY_CONFLICT_CURRENT_PAUSE = YES
*.NOTIFY_CONFLICT_CURRENT_RETRY = 2
*.NOTIFY_CONFLICT_THRESHOLD = 100
*.NOTIFY_DAILY_LIST_PROGRESS_TIME24 = 0700
*.NOTIFY_EXCEEDED_CYCLE_NUM = 2
*.NOTIFY_INCIDENT_LIMIT = 10
*.NOTIFY_INTERVAL_BETWEEN_CHECK = 5m
*.NOTIFY_ON_DDL = YES
*.NOTIFY_PEER_DOWN = ALL
*.NOTIFY_PROGRESS_DIFFERENCE_PERC = 10
*.NOTIFY_SCN_DIFFERENCE = 1000
*.NOTIFY_SEND_HEARTBEAT_TIME24 = 0800:1300
*.NOTIFY_SEQUENCE_DIFFERENCE = 10
*.NOTIFY_SUCCESS_EMAIL = OFF
*.NOTIFY_TIME_DIFFERENCE = 300