Sysdate returns “wrong” time (time with timezone). 25 February 2011Posted by David Alejo Marcos in Oracle 11.2, SQL - PL/SQL.
Tags: Oracle 11.2, SQL, SQL - PL/SQL
We are all used to execute sysdate to have the date + time of the database, what we are not so used to is to retrieve different values (depending of your timezone) from Oracle.
Sysdate, per Oracle documentation will do the following:
“SYSDATE returns the current date and time set for the operating system on which the database server resides. The data type of the returned value is DATE, and the format returned depends on the value of the NLS_DATE_FORMAT initialization parameter. The function requires no arguments. In distributed SQL statements, this function returns the date and time set for the operating system of your local database.”
Most people only reads the first line, where it says, it will return the date and time set for the operating system on which the database server resides; but right at the end, there is something we are all very familiar with, distributed SQL statements.
It is very hard to find a database not being accessed from different timezones than the server hosting it. Either because hosting is cheaper or because we have business in different countries.
If I execute a simple query to return the date and time from our US server:
SQL> alter session set nls_date_format='dd/mm/yyyy hh24:mi:ss'; Session altered. SQL> select sysdate from dual; SYSDATE ------------------- 24/02/2011 14:12:18 SQL> exit Disconnected from Oracle Database 11g Enterprise Edition Release 126.96.36.199.0 - 64bit Production With the Partitioning and Automatic Storage Management options
I receive the date and time in UTC:
[oracle@sssssssss ~]$ date Thu Feb 24 14:14:18 GMT 2011
From sqlplus in the UK:
C:\Documents and Settings\david.marcos>sqlplus daviddba@dddd SQL*Plus: Release 10.2.0.4.0 - Production on Thu Feb 24 14:14:30 2011 Copyright (c) 1982, 2007, Oracle. All Rights Reserved. Enter password: Connected to: Oracle Database 11g Enterprise Edition Release 188.8.131.52.0 - 64bit Production With the Partitioning and Automatic Storage Management options DAVIDDBA@dddd> DAVIDDBA@dddd> alter session set nls_date_format='dd/mm/yyyy hh24:mi:ss'; Session altered. Elapsed: 00:00:00.14 DAVIDDBA@dddd> select sysdate from dual; SYSDATE ------------------- 24/02/2011 09:14:55 Elapsed: 00:00:00.20 DAVIDDBA@dddd>
It returns the date and time in NYC.
Quite simple, we have a file on the server called /etc/sysconfig/clock. This file configures the system clock to Universal or Local time.
[oracle@ssss ~]$ cat /etc/sysconfig/clock ZONE="America/New_York" UTC=true ARC=false
Zone should be :
[oracle@sssssss ~]$ cat /etc/sysconfig/clock ZONE="UTC" UTC=true ARC=false
So clients also uses UTC. After amending the value we were back to business.
There is another quick way to fix the problem, providing you do not have local_listener configured on your system as you can manipulate the timezone for your sessions using your listeners. Let me explain, if you connect from the server, you will probably not use the listener, so sysdate should be the same than your servers date and time.
Starting the listener with different timezone (for example, using TZ OS environment variable) you will be able to have two different sysdate results (one if you select from the server and a different one if you connect using the listener).
So, to fix your problem you will need to do the following:
1.- Configure TZ variable on your server (i.e. export TZ=”UTC”)
2.- Stop listener
3.- Start listener
If you have local_listener, you will need to stop/start your database with the right TZ environment variable to fix the issue.
As always, questions are welcome.