Hi everyone!
I migrated from Oracle 12 to 19 recently and faced strange behavior of displaying timestamp with time zone values.
For example
Select SESSIONTIMEZONE, DBTIMEZONE, localtimestamp, systimestamp
from dual;
results on Oralce 19
+03:00
+00:00
05/04/2023 21:45:58.552596
08/04/2023 10:45:58.552594 +64:00
at the same time on Oralce 12:
+03:00
+00:00
05/04/2023 21:50:36.358303
05/04/2023 18:50:36.358297 +00:00
my current version is 16.2.98.1741
My colleagues use pl/sql developer and don't face this
could someone help me to fix this issue?
Guessing this is not a Toad issue, but rather how the dates might be set up in your Oracle 19. There could be many factors affecting how timestamps are produced on various systems.
You may want to check out these links to help you troubleshoot:
Is this post of any help at all.
I've had similar problems in the cloud. The application code used SYSDATE throughout and was getting the wrong times back as the cloud servers were all Oracle Linux with the UTC timezone. We were not allowed to change that.
If I remember correctly, we changed the code to use CURRENT_DATE instead.
SYSDATE returns the server time with apparently no adjustments for the session timezone. In our case, we got UTC from the server. Our sessions were in BST and thus …
This is a known issue when you are not using an Oracle Client. Use an Oracle client with Toad and the problem will go away.