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.02.4333(MAX edition) - Evaluation License expires in 30 days MINE IS running. Currently at plog 133 and SCN 3214278 (08/01/2014 06:17:57). APPLY IS running. Currently at plog 133 and SCN 3214206 (08/01/2014 06:17:55). Progress of replication dbvrep_orcl:MINE->APPLY: total/this execution -------------------------------------------------------------------------------------------------------------------------------------------- OE.CUSTOMERS: 99% Mine:1138/1138 Unrecov:0/0 Applied:1133/1133 Conflicts:0/0 Last:01/08/2014 06:17:58/OK OE.ADDRESSES: 99% Mine:1138/1138 Unrecov:0/0 Applied:1133/1133 Conflicts:0/0 Last:01/08/2014 06:17:58/OK OE.CARD_DETAILS: 99% Mine:1008/1008 Unrecov:0/0 Applied:1005/1005 Conflicts:0/0 Last:01/08/2014 06:17:58/OK OE.ORDER_ITEMS: 99% Mine:7615/7615 Unrecov:0/0 Applied:7596/7596 Conflicts:0/0 Last:01/08/2014 06:17:58/OK OE.ORDERS: 99% Mine:6143/6143 Unrecov:0/0 Applied:6127/6127 Conflicts:0/0 Last:01/08/2014 06:17:58/OK OE.INVENTORIES: 99% Mine:7468/7468 Unrecov:0/0 Applied:7450/7450 Conflicts:0/0 Last:01/08/2014 06:17:58/OK OE.LOGON: 99% Mine:7567/7567 Unrecov:0/0 Applied:7534/7534 Conflicts:0/0 Last:01/08/2014 06:17:58/OK -------------------------------------------------------------------------------------------------------------------------------------------- 7 tables listed.
In the above console line numbers are shown for clarity and each line number relate to the following explanation:
- Shows the version number and the edition
- Shows the MINE process is running. Which PLOG 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 OE.CUSTOMER. The replication is at 99%. 1138 records have been mined. 1133 records have been applied. No conflicts
- Replication statistics for table OE.ADDRESSES. The replication is at 99%. 1138 records have been mined. 1133 records have been applied. No conflicts
- Replication statistics for table OE.CARD_DETAILS. The replication is at 99%. 1008 records have been mined. 1005 records have been applied. No conflicts
- Replication statistics for table OE.ORDER_ITEMS. The replication is at 99%. 7615 records have been mined. 7596 records have been applied. No conflicts
- Replication statistics for table OE.ORDERS. The replication is at 99%. 6143 records have been mined. 6127 records have been applied. No conflicts
- Replication statistics for table OE.INVENTORIES. The replication is at 99%. 7468 records have been mined. 7450 records have been applied. No conflicts
- Replication statistics for table OE.LOGON. The replication is at 99%. 7567 records have been mined. 7534 records have been applied. No conflicts
- Separator
- Number of tables listed in the command console
If the Dbvisit Replicate console is not running then:
Connect to the souce server (dbv01) as oracle
Cd to the correct directory.
cd ~oracle/dbvrep_orcl
Start the Replication console:
./start-console.sh
The console can also be started on the target server *. The manual command to start the console is:
dbvrep --ddcfile /u01/oracle/dbvrep_orcl/dbvrep_orcl-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.
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.
sqlplus oe/oe@ttorcl_src
Run the query.
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.
sqlplus oe/oe@ttorcl_trg
Run the query.
SQL> select to_char(sum(order_total),'$999,999,999,999.00') "Total Orders" from orders; Total Orders -------------------- $7,317,074,993.00
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.
0 Comments