topic Re: Timestamp down to miliseconds - SAP Oracle DB in Qlik Replicate

Timestamp down to miliseconds - SAP Oracle DB

PedroHP — Mon, 16 Aug 2021 18:06:55 GMT

We are using the $AR_H_TIMESTAMP variable to get the timestamp from an SAP Oracle DB , but we are not receiving down to miliseconds (rounded to the next second).

Here is an example of the json that is being passed, the miliseconds are already not there. Is this a configuration on the Attunity side or Oracle DB side to have the miliseconds? WE are having a problem not being able to distinguish which UPDATE command came first when we have 2 commands on the same second for the same set of data.

header: no miliseconds on timestamp

body: always all the 9 digits for miliseconds come as zeroes

Re: Timestamp down to miliseconds - SAP Oracle DB

john_wang — Thu, 26 Aug 2021 13:20:08 GMT

Hello @PedroHP ,

I assume you are talking about the CDC stage.

This is not configuration issue nor Replicate limitation.

Replicate is log-based CDC product. When running CDC Replicate actually get the data from the Oracle redo log and the milliseconds are not part of that data therefore we always see zeros for the milliseconds part.

You may use column changeSequence to distinguish multiple UPDATEs command which occur in the same second.

Hope this helps,

Regards,

John.

Re: Timestamp down to miliseconds - SAP Oracle DB

PedroHP — Wed, 01 Sep 2021 10:29:08 GMT

Hi John,

we added the ChangeSequence variable but we are still getting the exact same sequence number when the timestamp is the same, see screenshot below for an example:

Is this expected or not in anyway? Is there something we should look for to avoid duplicate change sequence numbers?

Re: Timestamp down to miliseconds - SAP Oracle DB

john_wang — Wed, 01 Sep 2021 11:34:48 GMT

Hello @PedroHP ,

Please open a support ticket and upload task diagnostics package with

1. set source_capture/target_apply to Verbose

2. Reproduce the behavior and attach the diagnostics package.

Thank you,

John.