Page Comparison

The replication can be viewed from the Dbvisit Replication console. As soon as SwingBench starts generating DML changes, the tables that have changes applied to them will appear in the Replication Console.

Note
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.

\

No Format

Code Block

linenumbers	true

/ Dbvisit Replicate 2.7.02.433306(MAX edition) - Evaluation License expires in 30 days
MINE IS running. Currently at plog 13326 and SCN 3214278527369 (08/0112/2014 0615:1754:5709).
APPLY IS running. Currently at plog 13326 and SCN 3214206527392 (08/0112/2014 0615:1754:5510).
Progress of replication dbvrep_orclXE:MINE->APPLY: total/this execution
--------------------------------------------------------------------------------------------------------------------------------------------
OE
REPOE.CUSTOMERS:                  99%98%  Mine:113856/113856       Unrecov:0/0   Applied:55/55      Applied:1133/1133   Conflicts:0/0       Last:0112/08/2014 0615:1754:5811/OK
OEREPOE.ADDRESSES:     100%             99%  Mine:113855/1138  55     Unrecov:0/0   Applied:55/55      Applied:1133/1133   Conflicts:0/0       Last:0112/08/2014 0615:1754:5811/OK
OEREPOE.CARD_DETAILS: 100%              99%  Mine:100847/100847       Unrecov:0/0   Applied:47/47      Applied:1005/1005   Conflicts:0/0       Last:0112/08/2014 0615:1754:5811/OK
OEREPOE.ORDER_ITEMS:                99%95%  Mine:7615235/7615  235     Unrecov:0/0         Applied:7596224/7596224     Conflicts:0/0       Last:0112/08/2014 0615:1754:5811/OK
OEREPOE.ORDERS:          93%           99%  Mine:6143195/6143195       Unrecov:0/0         Applied:6127182/6127182     Conflicts:0/0       Last:0112/08/2014 0615:1754:5811/OK
OEREPOE.INVENTORIES:   95%             99%  Mine:7468228/7468228       Unrecov:0/0         Applied:7450217/7450217     Conflicts:0/0       Last:0112/08/2014 0615:1754:5811/OK
OEREPOE.LOGON:                    97%  99%  Mine:7567265/7567265       Unrecov:0/0         Applied:7534259/7534259     Conflicts:0/0       Last:0112/08/2014 0615:1754:5811/OK
--------------------------------------------------------------------------------------------------------------------------------------------
7 tables listed.
dbvrep>

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

Shows the version number and the edition, edition of the software (LTD, XTD, or MAX), and the type of license.
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
Shows the APPLY process is running. Which PLOG sequence and SCN the APPLY is processing and the (source) database time related to the SCN
Name of the replication
Separator
Replication statistics for table OEREPOE.CUSTOMER. The replication is at 99%98%. 1138 56 records have been mined. 1133 55 records have been applied. There are 0 conflicts.
Replication statistics for table OEREPOE.ADDRESSES. The replication is at 99%100%. 1138 55 records have been mined. 1133 55 records have been applied. There are 0 conflicts.
Replication statistics for table OEREPOE.CARD_DETAILS. The replication is at 99%100%. 1008 47 records have been mined. 1005 47 records have been applied. There are 0 conflicts.
Replication statistics for table OEREPOE.ORDER_ITEMS. The replication is at 99%95%. 7615 235 records have been mined. 7596 224 records have been applied. There are 0 conflicts.
Replication statistics for table OEREPOE.ORDERS. The replication is at 99%93%. 6143 195 records have been mined. 6127 182 records have been applied. There are 0 conflicts.
Replication statistics for table OEREPOE.INVENTORIES. The replication is at 99%95%. 7468 228 records have been mined. 7450 217 records have been applied. There are 0 conflicts.
Replication statistics for table OEREPOE.LOGON. The replication is at 99%97%. 7567 265 records have been mined. 7534 259 records have been applied. There are 0 conflicts.
Separator
Number of tables listed in the command console.
The Replication Console command prompt.

Note

TIP 1

If the Dbvisit Replicate console is not running then:

Connect to the souce server (dbv01) as oracle.
Cd to the correct directory.
No Format
cd ~oracle/dbvrep_orclXE
Start the Replication console:
No Format
./start-console.sh
The console can also be started on the target server *. The manual command to start the console is:
No Format
dbvrep --ddcfile /u01/app/oracle/dbvrep_orclXE/dbvrep_orclXE-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.

Note

TIP 12

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:

No Format
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"

Note

TIP 23

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

No Format
dbvrep> list stats dbvrep> list stats all dbvrep> list stats OEREPOE.ORDER_ITEMS

Note

TIP 34

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:

No Format

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

Confirm the data is replicated

To confirm that the data is replicated the following query can be run on both the source and the target database.

1. Connect to the source database.

No Format
sqlplus oe/oe@ttorcl_src

Run the query.

No Format
SQL> select to_char(sum(order_total),'$999,999,999,999.00') "Total Orders" from orders; Total Orders -------------------- $7,317,074,993.00

2. Connect to the target database.

No Format
sqlplus oe/oe@ttorcl_trg

Run the query.

No Format
SQL> select to_char(sum(order_total),'$999,999,999,999.00') "Total Orders" from orders; Total Orders -------------------- $7,317,074,993.00

Note

This query should give the approximately the same number on the source and target database when the replication is < 100%.

Run the queries several times to see that the numbers are updating on both the source and target database.

If the replication is at 100% then the numbers will be the same.

...

Versions Compared

Old Version 20

New Version Current

Key

Confirm the data is replicated