...
This query uses database link created before and checks for any rows, that are in source database and are not present in target database and vice versa. If it returns some rows, than something bad happened.
Batch DML operation:
Lets update all rows in REPOE.TABLES table on SOURCE database:
| No Format | ||
|---|---|---|
| ||
SQL> conn repoe/repoe@SOURCE
Connected.
SQL> update tables set LAST_ANALYZED=sysdate;
11 rows updated.
SQL> commit;
Commit complete. |
Again, lets check the dbvrep console:
| No Format | ||
|---|---|---|
| ||
| Dbvisit Replicate 2.8.04(MAX edition) - Evaluation License expires in 30 days
MINE is running. Currently at plog 33 and SCN 792004 (06/08/2017 22:21:17).
APPLY is running. Currently at plog 33 and SCN 791986 (06/08/2017 22:21:13).
Progress of replication replicate:MINE->APPLY: total/this execution
--------------------------------------------------------------------------------------------------------------------------------------------
REPOE.CARD_DETAILS: 100% Mine:1/1 Unrecov:0/0 Applied:1/1 Conflicts:0/0 Last:08/06/2017 22:04:48/OK
REPOE.TABLES: 100% Mine:22/22 Unrecov:0/0 Applied:22/22 Conflicts:0/0 Last:08/06/2017 22:20:53/OK
-------------------------------------------------------------------------------------------------------------------------------------------- |
From this output, you can see, that one command, that was run on source database and changes 11 rows, created 11 single row changes. Replicate is not replicating commands, but only rows changed.