You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

ADW not showing sysdate correctly as per timezone

edited Aug 17, 2021 12:48PM in Autonomous Database 5 comments

Content

Hi Team,

We have deployed ADW in a shared infra and currently facing issues to show "sysdate" correctly as per the customer defined timezone.

Our DB timezone parameter is set as  "Australia/Melbourne" and showing correctly when querying 

select dbtimezone from dual;

However, when we query 

select sysdate from dual

The result is showing date with "UTC" timezone which I understand is the OS timezone.

Is there any way to change the OS timezone/sysdate to show correctly as per the dbtimezone parameter?

 

We have ODI marketplace for data integrations and due to this ADW sysdate issue, all the integration log timestamp is also showing in the UTC timezone since our ODI-M repository is hosted in the ADW. Our ODI-M compute instance OS timezone is  correctly set as "Australia/Melbourne" which enables our integration to run as per the "Australia/Melbourne" data load schedule.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!