topic Bi-directional loading "attrep_loopback_prevention" Table in Qlik Replicate

Bi-directional loading "attrep_loopback_prevention" Table

Manjunathps — Fri, 27 Oct 2023 04:22:15 GMT

Hi Everyone,

I'm trying Bi-direction task between the oracle and postgres-aurora endpoints,

as soon as I start the task, there is error saying "attrep_loopback_prevention" doesn't exists.

So I had to manually create the table at the oracle source.

Is it not that the "attrep_loopback_prevention" Table should be created on its own, as soon I start the task?

Thank you,

Manjunath

Re: Bi-directional loading "attrep_loopback_prevention" Table

SachinB — Fri, 27 Oct 2023 04:29:57 GMT

Hello @Manjunathps ,

Thank you for reaching out to the Qlik community!

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.

refer the below articles for the same.

https://community.qlik.com/t5/Official-Support-Articles/Using-Bi-Directional-to-Ignore-Transactions/ta-p/1735968

https://community.qlik.com/t5/Official-Support-Articles/Setting-up-Bi-Directional-Replication/ta-p/1735967

Regards,

Sachin B

Re: Bi-directional loading "attrep_loopback_prevention" Table

DesmondWOO — Fri, 27 Oct 2023 11:11:25 GMT

Hi @Manjunathps ,

"attrep_loopback_prevention" should be created by Replicate automatically. If it fails to do so, you can enable TRACE/VERBOSE logging on TARGET_APPLY to check why.

Regards,
Desmond