Suggest an Idea

[AndreasFenske]

When Qlik Replicate is replicating timestamp fields from Oracle to Kafka (Avro), then the Oracle timestamps are taken 1:1 and written as unix epoch times into Kafka. However in our case the Oracle timestamp is in CET/CEST (Zurich timezone) and the unix epoch time is in UTC. Writing the Oracle timestamp 1:1 to Kafka as UTC results in a wrong timestamp.

Please see also the discussion here: https://community.qlik.com/t5/Qlik-Replicate/Timezone-Conversion-Oracle-CET-to-Kafka-Avro-UTC/m-p/18...

Our suggestion:

When writing timestamps from Oracle to Kafka (Avro) as unix epoch times, Qlik Replicate should check the Database timezone information and use a conversion. In our case convert CET/CEST to UTC correctly and then write it as unix epoch time to Kafka.

Furthermore, related to this issue:

Functions like $AR_H_TIMESTAMP are using local server time (of Qlik Replicate server) and are also writing the timestamp 1:1 as UTC into Kafka, although they are not UTC. But this is an issue and not an idea in my opinion. I will create a support case for that.

[Wim]

Wouldn't this help for you?:

https://community.qlik.com/t5/Suggest-an-Idea/Qlik-Replicate-convert-all-timestamps-to-localtime/idi...

[AndreasFenske]

"Local time" in that case would be the time of the server Qlik Replicate is running on, which might be not necessarily the timezone the Oracle database is configured.

If both are the same, your suggestion (creating a global rule for all columns) might be a workaround.

But to have a solution independent of the Qlik Replicate server it would be best do be able to configure the timezone in the Oracle Endpoint Connection or Qlik can identify the timezone itself in the source database.

[Nulee_Massaro]

We are currently in the process of moving all ideations to a new system. In an effort to make this migration easier, we are closing older ideations that did not see a lot of activity (likes/comments). If you are still interested in this enhancement, please open a new ideation so it repopulates as "new" in our system. 

Thank you. Let me know if you have any questions!