(Qlik Replicate) Handling FK Violations in Oracle to PostgreSQL Replication

Vinicius_Luiz — Wed, 04 Oct 2023 21:07:01 GMT

Hello everyone, to make my question easier to understand, here are two scenarios:

Scenario 1. In a replication task (Oracle -> Oracle). When replicating a record that will have an FK violation, the data error will be stored in the "attrep_apply_exceptions" table in the target database and the task continues to operate normally.

Scenario 2. In a replication task (Oracle -> PostgreSQL). When replicating a record that will have an FK violation, the data error is stored in the table log, and in addition, the transaction is pending in the task until the error is resolved.

Scenario 2 is problematic because data replication is completely affected due to a record with FK violation (figure 1). Is there any way to make the registry with violated FK treated the same way as in scenario 1? It is important to highlight that the Error Handling configuration is the same in both scenarios.

Figure 1

Re: (Qlik Replicate) Handling FK Violations in Oracle to PostgreSQL Replication

Dana_Baldwin — Wed, 04 Oct 2023 21:24:09 GMT

Hi @Vinicius_Luiz

I don't have an answer to your direct question, but you can avoid issues with FK violations by running the tasks in transactional apply mode, so that every transaction on the target mimics what happens on the source in the same order. The obvious downside to this is it performs much slower. Just wanted to point this out in case you were not aware.

Dana

topic Re: (Qlik Replicate) Handling FK Violations in Oracle to PostgreSQL Replication in Qlik Replicate

(Qlik Replicate) Handling FK Violations in Oracle to PostgreSQL Replication

Re: (Qlik Replicate) Handling FK Violations in Oracle to PostgreSQL Replication