topic No Records beeing inserted to target after applying apply Conflicts Settings. in Qlik Replicate

No Records beeing inserted to target after applying apply Conflicts Settings.

Chirag_ — Mon, 29 Apr 2024 11:57:42 GMT

Hi team,

We are facing an issue at CDC. On the replicate server; in the apply changes tab, incremental changes are seen but we cannot see the changes(specifically inserts being appended) at target side. we have tried keeping the logging level ( Performance to Trace, Target Apply to Verbose) but we cannot find any possible clue.

FYI: we are using DR (Oracle ) as a source and Oracle as a Target, we have turned on the Apply conflict setting
(Duplicate key when applying an INSERT: Update the existing target record) as we are facing violation error(ORA-00001: unique constraint primary key violated) whenever there is an update.

Table information: Table contains Primary Key, is around 0.4GB, has 30 columns and has good frequency of incremental changes.

Regards,
Chirag.

Re: No Records beeing inserted to target after applying apply Conflicts Settings.

john_wang — Mon, 29 Apr 2024 13:43:41 GMT

Hello @Chirag_ ,

Thanks for reaching out to Qlik Community!

Looks to me the source and target are out of synchronization so you got ORA-00001 frequently in the default Error Handling Policy. After change to UPSERT mode, the INSERT operations will be converted to UPDATE operations if PK violation occurring. Not sure if you can RELOAD the task to get the data synchronized.

We may troubleshooting the current issue by:

1. Sert SOURCE_CAPTURE/TARGET_APPLY to Verbose, recreate the issue then check the task log file to understand the root case. Please do not forget to decrypt the task log file .

2. Enable the Store Changes to get the record values from Change Tables to get helpful clue.

Hope this helps.

John.

Re: No Records beeing inserted to target after applying apply Conflicts Settings.

Chirag_ — Tue, 30 Apr 2024 09:31:18 GMT

Yes, we can see the following warning (Using standby database could have caused the missing events problem during Full Load and CDC synchronization).

Thanks & Regards,
Chirag