What exactly does Timestamp represent in a message created by Qlik Replicate?

[MoeE]

Hi,

I'm looking at the documentation for Amazon Kinesis and I am confused as to what exactly this timestamp represents. My assumption is that it represents the time at which the change occurred on the source database. Is this correct?

Furthermore, can someone please help me understand the ChangeSequence field. Is this field only created by Qlik Replicate for each change that the task needs to apply? If I was to replay changes by timestamp, would they have the same change sequence or would it change?

Regards,

Mohammed

[DesmondWOO · Accepted solution]

Hi @MoeE ,

Wishing you a prosperous 2025!

Please find my answers to your questions below:

1) timestamp
You are right. It's the timestamp that change occurred in the source database. 

2) changeSequence
It should be the same as header__change_seq in the __CT table. The time component typically refers to the transaction's commit time, while the remaining part is an internal change number generated by Replicate. For instance, if your transaction includes multiple updates, they will share the same commit time. Therefore, we use an internal change number to differentiate between them.

If you resume the task using an earlier timestamp, the internal change number will be reset, leading to a different change number for the same change record. Consequently, the change sequence will be different.

Regards,
Desmond

[MoeE]

Hi Desmond,

Thank you!

Regards,

Mohammed

[Kunal9889]

Hello Desmond,

1) timestamp
You are right. It's the timestamp that change occurred in the source database. 

Q) Are you referring to commit timestamp? Can we piece of source code around the headers from where it is executed with respect to oracle database