topic Re: Differences in millisecond population with AR_H_COMMIT_TIMESTAMP in Qlik Replicate

Differences in millisecond population with AR_H_COMMIT_TIMESTAMP

qlik_admin_lm — Wed, 23 Oct 2024 15:27:13 GMT

We are replicating data from both Oracle and DB2 sources. In both cases we are using the AR_H_COMMIT_TIMESTAMP variable to populate the commit time of the transaction. We are noticing that values are populated to the millisecond for the DB2 source but not for the Oracle sources. We are wondering why for the Oracle sources is commit timestamp only populated down to the second level and not the microsecond level.

Re: Differences in millisecond population with AR_H_COMMIT_TIMESTAMP

sureshkumar — Thu, 24 Oct 2024 01:10:51 GMT

Hello @qlik_admin_lm

Kindly try using the function strftime in the transformation and pass the AR_H_COMMIT_TIMESTAMP value into it.

https://help.qlik.com/en-US/replicate/May2024/Content/Global_Common/Content/SharedEMReplicate/Customize%20Tasks/tasks_expressOther.htm#Date

Regards,
Suresh

Re: Differences in millisecond population with AR_H_COMMIT_TIMESTAMP

qlik_admin_lm — Wed, 15 Jan 2025 22:12:13 GMT

We have it configured like this in the Global Transformation:

strftime("%Y-%m-%d %H:%M:%f", $AR_H_COMMIT_TIMESTAMP, "utc")

Re: Differences in millisecond population with AR_H_COMMIT_TIMESTAMP

DesmondWOO — Thu, 16 Jan 2025 04:43:34 GMT

Hi @qlik_admin_lm ,

I believe this is a restriction of the Oracle database. For example, in the V$LOGMNR_CONTENTS view, the datatype of COMMIT_TIMESTAMP is DATE, which means the value is limited to seconds.

Regards,
Desmond