Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
ALERT: The support homepage carousel is not displaying. We are working toward a resolution.

Using Bi-Directional to Ignore Transactions

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
David_Fergen
Former Employee
Former Employee

Using Bi-Directional to Ignore Transactions

Last Update:

Feb 9, 2021 1:10:54 PM

Updated By:

David_Fergen

Created date:

Aug 14, 2020 10:15:53 AM

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. 

Labels (1)
Version history
Last update:
‎2021-02-09 01:10 PM
Updated by: