Differences in millisecond population with AR_H_COMMIT_TIMESTAMP

[qlik_admin_lm]

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.

[sureshkumar]

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/Custom...

Regards,
Suresh

[qlik_admin_lm]

We have it configured like this in the Global Transformation: 

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

and it is still not producing the milliseconds.

[DesmondWOO]

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