Using Bi-Directional to Ignore Transactions

David_Fergen — Tue, 09 Feb 2021 18:10:54 GMT

These are directions for how to use the bi-directional task in a one-way mode to ignore transactions.

First create the attrep_loopback_prevention manually in the source:

( "task_name" VARCHAR2(128) NOT NULL ENABLE, "timestamp" TIMESTAMP (0), CONSTRAINT "HRattrep_loopback_prevention" PRIMARY KEY ("task_name") ENABLE, SUPPLEMENTAL LOG DATA (PRIMARY KEY) COLUMNS )

Make sure to insert a dummy row into the new table:

insert into "attrep_loopback_prevention" values ('JUNK', sysdate);

When doing an operation make sure to ignore then include an operation against this table:

delete from job_history where employee_id > 999; update "attrep_loopback_prevention" set "timestamp" = sysdate; commit;

Create a bi-directional task.

DOWNSIDE: Every transaction applied to the target will update the attrep_loopback_prevention table.

article Using Bi-Directional to Ignore Transactions in Official Support Articles

Using Bi-Directional to Ignore Transactions