Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Streamlining user types in Qlik Cloud capacity-based subscriptions: Read the Details
cancel
Showing results for 
Search instead for 
Did you mean: 
MoeE
Partner - Specialist
Partner - Specialist

Timestamp timezone conversion

Hi Support,

There is a task that goes from Oracle to ADLS Gen 2. There is a column in the source table that is of the datatype "Timestamp with local timezone". 

The issue is that after the full load completes, the timestamp in ADLS appears one hour ahead.

E.g The timestamp is 7:30 AM in the source Oracle table, and 8:30 AM in the ADLS target table. 

For context, Replicate, Oracle and ADLS are in the AEST timezone. But they are using daylight savings time so the time is moved forwards one hour automatically so that it is correct.

My initial thoughts are that two things could be happening.

Scenario 1 - Replicate is actually adding one hour to the record.

Scenario 2 - It is being cast as the ADLS time which adds one hour to the time. 

My question is, how would I be able to identify whether Qlik Replicate is changing to add one hour? I've already tried increasing source_capture and source_unload logging to verbose but it has no indication as to what datatypes and timezone that the data is being cast into. 

I know that the datatype mapping goes like this.

Oracle -> Replicate

Timestamp -> String

MoeyE_0-1729050416507.png

 

Replicate -> ADLS. 

String -> String

MoeyE_1-1729050459106.png

(ADLS's parquet has a primitive and logical type) 

 

Update: I figured out that you can use the logger called Target_Load set to verbose to view the target metadata.

 

Regards,

Mohammed

 

Labels (1)
1 Solution

Accepted Solutions
SachinB
Support
Support

Hello @MoeE ,

Thanks for reaching out to Qlik community portal.

 

In order to identify what date is being sent to target from replicate you enable below internal parameter at target endpoint 

Please go to Manage endpoint --> Target Endpoint--> Advance Tab -->Click internal parameter

Add keepCSVFiles and make sure they are checked.

This will generate the load files which are sent being sent as part of replication to the target environment and you can verify the data in this file

C:\Program Files\Attunity\Replicate\data\tasks\task_name\applied_files

 

Regards,

Sachin B

 

 

 

 

View solution in original post

2 Replies
SachinB
Support
Support

Hello @MoeE ,

Thanks for reaching out to Qlik community portal.

 

In order to identify what date is being sent to target from replicate you enable below internal parameter at target endpoint 

Please go to Manage endpoint --> Target Endpoint--> Advance Tab -->Click internal parameter

Add keepCSVFiles and make sure they are checked.

This will generate the load files which are sent being sent as part of replication to the target environment and you can verify the data in this file

C:\Program Files\Attunity\Replicate\data\tasks\task_name\applied_files

 

Regards,

Sachin B

 

 

 

 

MoeE
Partner - Specialist
Partner - Specialist
Author

Hi Sachin,

 

Thanks for the help. I will try this.

 

Regards,

Mohammed