Kudu time difference

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Kudu time difference

Roshan
Hello Erman,

I noticed will pushing data to Kudu using Striim - data with TIMESTAMP are being substrated by 4 hours on target Kudu. Source and target server have same timezone.


[root@RH-DATWHSE-DEV logs]# date +"%Z %z"
+04 +0400

Kindly advise.

Regards,

Roshan

Reply | Threaded
Open this post in threaded view
|

Re: Kudu time difference

ErmanArslansOracleBlog
Administrator
Your timezone is +4, and your data in kudu seems at +0
So, you have a timezone problem probably in kudu. I don't know where and how you import your data to kudu, but I would check the definitions and configurations on the kudu side in the first place.
Reply | Threaded
Open this post in threaded view
|

Re: Kudu time difference

Roshan
Thanks. I use Striim to load the data. Do you know on Kudu which parameters to check?  The server time is in sync with Striim server time.
Reply | Threaded
Open this post in threaded view
|

Re: Kudu time difference

ErmanArslansOracleBlog
Administrator
I've never been involved with Kudu until now. Better ask the Kudu experts.
Reply | Threaded
Open this post in threaded view
|

Re: Kudu time difference

Roshan
Hi Erman,

there is a date function in Striim which adds hours to a timestamp field.

https://www.striim.com/docs/en/date-functions.html

I have tried to use in COLUMNMAP  (DADD(ts, DHOURS(4)) but this format is not acceptable.

Incorrect column mapping is specified in {TRANS_DATE_D=DADD(TRANS_DATE_D, DHOURS(4)),CHRG_FROM_DATE_D=DADD(CHRG_FROM_DATE_D, DHOURS(4)),CHRG_TILL_DATE_D=DADD(CHRG_TILL_DATE_D, DHOURS(4)),DUE_DATE_D=DADD(DUE_DATE_D, DHOURS(4)),INVOICE_GENERATED_ON_D=DADD(INVOICE_GENERATED_ON_D, DHOURS(4)),DELIVERED_ON_D=DADD(DELIVERED_ON_D, DHOURS(4)),EMISSION_DATE_D=DADD(EMISSION_DATE_D, DHOURS(4))}