Versions Compared

Old Version 19

changes.mady.by.user Arjen Visser

Saved on

compared with

New Version Current

changes.mady.by.user Arjen Visser

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The replication can be viewed from the Dbvisit 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. 

...

  1. Shows the version number and the edition
  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 OE.CUSTOMER. The replication is at 99%. 1138 records have been mined. 1133 records have been applied. There are 0 conflicts.
  7. Replication statistics for table OE.ADDRESSES. The replication is at 99%. 1138 records have been mined. 1133 records have been applied. There are 0 conflicts.
  8. Replication statistics for table OE.CARD_DETAILS. The replication is at 99%. 1008 records have been mined. 1005 records have been applied. There are 0 conflicts.
  9. Replication statistics for table OE.ORDER_ITEMS. The replication is at 99%. 7615 records have been mined. 7596 records have been applied. There are 0 conflicts.
  10. Replication statistics for table OE.ORDERS. The replication is at 99%. 6143 records have been mined. 6127 records have been applied. There are 0 conflicts.
  11. Replication statistics for table OE.INVENTORIES. The replication is at 99%. 7468 records have been mined. 7450 records have been applied. There are 0 conflicts.
  12. Replication statistics for table OE.LOGON. The replication is at 99%. 7567 records have been mined. 7534 records have been applied. There are 0 conflicts.
  13. Number of tables listed in the command console. 
Note

TIP 1

If the Dbvisit Replicate console is not running then:

  1. Connect to the souce server (dbv01) as oracle.

  2. Cd to the correct directory.

    No Format
    cd ~oracle/dbvrep_orcl

  3. Start the Replication console:

    No Format
    ./start-console.sh

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

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

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

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

No Format
dbvrep> list stats
dbvrep> list stats all
dbvrep> list stats OE.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.

 

...