Oracle Analytics Forum

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Setting a Session Variable for User Time Zone in OAS 2025 DV

Received Response
33
Views
2
Comments

Hi all,

We are currently using Oracle Analytics Server 2025 (DV) and want to understand how time zones are handled at the session level

Questions?

  • In OAS 2025 DV, can we set a session variable that dynamically captures the user’s time zone (e.g., based on browser locale, user profile, or authentication context)?
  • If yes:
    • How is this configured (administration, RPD, or DV)?
    • Is it available for use in DV data flows / calculations?
    • Does it respect Daylight Saving Time (DST) transitions automatically?
  • If not, what is the recommended pattern for ensuring time zone–aware date/time calculations and visualizations in DV?

We are specifically looking for a method that does not require hard-coding time offsets per user but rather uses a variable accessible at runtime.

Thanks in advance for insights.

Tagged:

Answers

  • Hi,

    Here is some general information for you to consider.

    OAC uses GMT.

    OAS will use your server time..

    As for session variables in OAS, in What's Notable and Different, TIMEZONE session variable is disabled by default and marked for deprecation (System Configuration)

    You can enable it by following this MyOracle Support article.

    How To Enable Oracle Analytics Server (OAS) Deprecated Features That Are Disabled By Default (KB118837)

    As an Administrator, in the Analytics Console, you can configure 'Default User Preferred Time Zone', 'Default Data Offset Time Zone' and 'Default Time Zone for Date Calculations'

    See: About System Settings > Format Options

    The Console settings will take precedence over anything configured in the Presentation Server configuration file.


    Also review this key section of the documentation:
    What Is the Precedence Order for Time Zones?

    I will let others comment about their experiences. I think some of the answers to your questions may depend on Subject Area vs. datasets, etc.

  • As per my experience, OAS 2025 DV does NOT expose a built-in session variable that dynamically captures the user’s browser or local time zone. We cannot directly access browser locale or client time zone in RPD or DV calculations. Time zone handling is primarily Server-side or Database-driven.