striim date function

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

striim date function

Roshan
Hello Erman,

kindly advise why there is discrepency in DATE and TIMESTAMP WITH TIMEZONE (4 hours) when replicating from Oracle to Kudu? We set Indian/Mauritius as timezone in server.sh

Thanks,

Roshan
Reply | Threaded
Open this post in threaded view
|

Re: striim date function

ErmanArslansOracleBlog
Administrator
Please revise your question Roshan.
Please give me the details about that discrepency.

Kudu is not in my interest bytheway.. But I will try to help.. (but you need to make me understand the issue better)
Reply | Threaded
Open this post in threaded view
|

Re: striim date function

Roshan
Hi,

in fact there was a time discrepency of 4 hours for DATE and TIMESTAMP WITH TIMEZONE fields on target. There was an error in Striim's UDF file - they had do add the code to handle these datatypes.

It is ok now.
Reply | Threaded
Open this post in threaded view
|

Re: striim date function

ErmanArslansOracleBlog
Administrator
Okay they found a workaround then..
What do you have in the Striim CDC records? Does Striim supply everything that need to be there in order to populate those fields according to the timezone info of the target? If everything ok there, then the issue should be in the Kudu side...
Reply | Threaded
Open this post in threaded view
|

Re: striim date function

Roshan
In fact the time on Kudu had a discrepency of 4 hours as compared to Oracle date fields (source). Striim provided a UDF (jar file) which contains code to add 4 hours for any timestamp/date datatypes coming from source Oracle stream.

The UDF had an issue - date fields were set to Joda time which is correct while timestamp and timestamp with timezone were set to local time. So they did the correction in the UDF and set  timestamp and timestamp with timezone to JODA time.