Missing $AR_H_TIMESTAMP update on Oracle target when source DB2 AS400 performs UPDATE

[EY_]

Dear Support Team,

We are currently replicating data from a DB2 AS400 source to an Oracle target using Qlik Replicate.

We have added a new column on the Oracle target table to store the $AR_H_TIMESTAMP provided by Qlik Replicate, which works correctly for INSERT operations — the timestamp is properly populated.

However, we have noticed that when the source DB2 AS400 performs an UPDATE, the $AR_H_TIMESTAMP value does not get updated on the Oracle target. Our expectation is that any replicated UPDATE should also refresh the $AR_H_TIMESTAMP to reflect the latest change time.

Could you please advise if this is expected behavior, or if there is a configuration or workaround needed to ensure that $AR_H_TIMESTAMP is updated for UPDATE operations as well?

Looking forward to your guidance. Thank you.

[Dana_Baldwin]

Hi @EY_ 

I don't see a documented limitation here, and the User Guide is written in such a way that I would expect updates to refresh this value - but it does not state that explicitly.

On the source, are you logging both before & after images?

If someone does not provide a definitive answer on this we may request you to open a support case so we can look into it further. We would need a diagnostics package for the task and task logs from a time frame that updates were processed (the diagnostics package only gathers the last 3 days worth of task logs). In fact you might increase logging for Source_Capture & Target_Apply briefly while the task runs and you test some updates to see if we can gather more information.

Thanks,

Dana

[narendersarva]

Hi @EY_ 

AR_H_TIMESTAMP is the time associated with the change record and indicates when the change happened on the source.

The AR_H_COMMIT_TIMESTAMP indicates when the change was committed on the source.

Both are represented in UTC.

Please refer below link for additional insights.

How to calculate time of changes within Qlik Repli... - Qlik Community - 1891108

Thanks
Naren

[john_wang · Accepted solution]

Hello @EY_ ,

It works for both INSERT and DELETE operations, maybe some special settings (eg filter) lead it not being updated.

See my sample, in transform $AR_H_TIMESTAMP is introduced:

The ID=2 reflects the UPDATE operation in source table:

Regards,

John.