My Oracle Support Banner

Sysdate Gives Wrong Time After ODA Upgrade to 19.x (Doc ID 2757128.1)

Last updated on MARCH 04, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 19.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

After an upgrade to 19.x the times are no longer correct.

In this case they are showing a one hour difference.


All client/server connections for all databases on the ODA server give the wrong sysdate after upgrade from 18.8.0.0 to 19.9.0.0.

select 'sysdate' ,to_char (sysdate, 'dd-mm-yyyy hh24:mi:ss') from dual
   union
select 'localtimestamp' ,to_char (LOCALTIMESTAMP) FROM DUAL

returns:

localtimestamp 01-03-21      14:35:50....
sysdate            01-03-2021  13:35:50

 More

====

more /tmp/jobtime.txt
SQL> select to_char(systimestamp, 'DD/MM/YYYY HH24:MI:SS TZR') from dual;

TO_CHAR(SYSTIMESTAMP,'DD/MM/YYYYHH24:MI:SSTZR')
---------------------------------------------------------------------------
02/03/2021 09:50:09 +01:00

SQL> select to_char(sysdate, 'DD/MM/YYYY HH24:MI:SS') from dual;

TO_CHAR(SYSDATE,'DD/MM/YYYYHH24:MI:SS')
---------------------------------------------------------------------------
02/03/2021 09:50:14


SQL> select * from SYS.SYSTIME_TEST;

COL1
------------------------------
02/03/2021 08:50:44 +00:00
02/03/2021 08:50:44
+00:00

This means the database was *started* with +00:00 but the *current* OS timezone is +01:00.
this means the database was started with an other OS timezone than currently defined

Changes

Upgrade of the ODA to 19.x from 18.x


Comment Not confirmed if the same problem can also occur from a 19.x to a 19.y version but should not be ruled out

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.