Last updated on DECEMBER 05, 2016
Applies to:Oracle Database - Standard Edition - Version 22.214.171.124 and later
Oracle Database - Enterprise Edition - Version 126.96.36.199 and later
Information in this document applies to any platform.
Possible reasons to follow this note:
* The result / timezone of SYSDATE and SYSTIMESTAMP need to be changed.
Please DO check first of all if the result that need to be changed is SYSDATE or SYSTIMESTAMP !
Ask the application vendor or developers what exactly they do to "get the database time".
In 99% of the case it is SYSDATE or SYSTIMESTAMP , but it's better to be sure.
There are for example other functions who give the time in a timezone defined by the *client* -> <Note 340512.1> Timestamps & timezones - Frequently Asked Questions 9) What is the difference between CURRENT_DATE, LOCALTIMESTAMP and CURRENT_TIMESTAMP?
If the application vendor/programmers say they use SYSDATE / SYSTIMESTAMP and this need to changed to an other time /timezone then this is the note to follow.
For "wrong time" issues please see <note 1627439.1> How to diagnose wrong time ( SYSDATE and SYSTIMESTAMP) after DST change , server reboot , database restart or installation when connecting to a database on an Unix server
This may be needed due an application requirement .
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms