...
When we see in the console, that the row was sucessfully replicated to the target database, we should check, if it is correctly replicated. Connect to target database as user repoe/repoe and run following command:
| Code Block | ||||
|---|---|---|---|---|
| ||||
select * from REPOE.CARD_DETAILS where card_type='REPOE_TEST';
CARD_ID CUSTOMER_ID CARD_TYPE CARD_NUMBER EXPIRY_DATE I SECURITY_CODE
---------- ----------- ------------------------------ ----------- ------------------ - -------------
750005 1287 REPOE_TEST 9102450385 22-JAN-15 Y 1000 |
...
REPOE.LOGON and REPOE.ORDERENTRY_METADATA. We will use the REPOE.LOGON table for duplicate creation. Run following insert on source database to create duplicity:
| Code Block | ||||
|---|---|---|---|---|
| ||||
REPOE@TTORCL_SRC> insert into repoe.logon select * from repoe.logon where logon_id=1000000; 1 row created. REPOE@TTORCL_SRC> commit; Commit complete. |
...
Check, that the duplicated row also exists in the target database.
| Code Block | ||||
|---|---|---|---|---|
| ||||
REPOE@TTORCL_trg> select * from repoe.logon where logon_id =1000000 order by customer_id; LOGON_ID CUSTOMER_ID LOGON_DATE ---------- ----------- ------------------ 1000000 496840 31-MAR-06 1000000 496840 31-MAR-06 |
...
On source database run following update command.
| Code Block | ||||
|---|---|---|---|---|
| ||||
REPOE@TTORCL_SRC> update repoe.logon set logon_id=logon_id*100 where logon_id =1000000; 2 rows updated. REPOE@TTORCL_SRC> commit; Commit complete. |
Check in the console, that we have really created the conflict
| Code Block | ||
|---|---|---|
| ||
REPOE.LOGON: 33% Mine:3/3 Unrecov:0/0 Applied:1/1 Conflicts:1/1 Last:23/01/2015 04:05:29/RETRY:Command affected 2 row(s). |
...
Connect to dbvrep console and run command list conflict
| Code Block | |
|---|---|
| List conflict example | dbvrep> list conflict
Information for conflict 32010159940 (current conflict):
Table: REPOE.LOGON at transaction 000a.01f.000001df at SCN 653532
SQL text (with replaced bind values): update "REPOE"."LOGON"
set "LOGON_ID" = 100000000
where (1=1)
and "LOGON_ID" = 1000000
and "CUSTOMER_ID" = 496840
and "LOGON_DATE" = to_date('2006.03.31 04:18:40','yyyy.mm.dd hh24:mi:ss')
Error: Command affected 2 row(s).
Handled as: PAUSE
Conflict repeated 21 times. |
...
Now we have to resolve the conflict in order to let apply process to continue. Lets choose ignore resolution type:
| Code Block | title | Resolving conflict 1
|---|
dbvrep> resolve conflict 32010159940 as ignore Conflict resolution set. |
...