Previously, the SYSDATE function in Oracle returned the correct local time (UTC+7), matching the OS settings. However, today it seems to return the time in UTC instead.
Here's the current output from timedatectl on the OS:
Local time: Wed 2025-04-16 15:53:03 +07
Universal time: Wed 2025-04-16 08:53:03 UTC
RTC time: Wed 2025-04-16 08:53:03
Time zone: Asia/Bangkok (+07, +0700)
- No OS changes have been made
- The database was working as expected before (SYSDATE reflected UTC+7), but now it's 7 hours behind (as if using UTC)
Questions:
- What could cause
SYSDATE to no longer follow the OS time zone, even though timedatectl shows the correct local time?
- Could Oracle be using a different environment or configuration for its internal time source?
- Where should I look to debug this further?