Enable Local Timezones for OAC Usage Tracking Logging

Dave Rynne

OAC Currently writes Usage tracking records in UTC format.

However, We have predominantly NZT stamped data in our warehouse.
Adding the UTC format usage tracking data makes it difficult to use OAC to present stats on USage Tracking in a sensible format.

We have to look at ETLing the usage data and converting the timeformat to NZT which is clunky.
If we could allow OAC to be configured to write the data in a preferred timezone, it would make like a lot easier.

Bret Grinslade - Oracle Analytics-Oracle

Have you considered adding a prep step in a dataset or subject are to convert to an easier to use format? Usage tracking is logged in UTC for clarity on the meaning. This can be easily handled in queries or at the reporting level.

For example you could use:

TIMESTAMPADD(SQL_TSI_HOUR, +12 ,TIMECOLUMNHERE) 

Gabby Rubin-Oracle

In addition, creating a view in the database with the time conversion might be another easy solution that does not require ETL or data movement.

Jay Griffeth

Here's the SQL statement I used for converting from UTC to US Central:

FROM_TZ(CAST(etl_start_date AS TIMESTAMP ), 'UTC' ) AT TIME ZONE 'US/Central' as etl_start_date_local

Hope this helps.