1. one connect using the ENV parameters - this shows the correct time as per OS date/time
2. the other using @SID_NAME - this shows time 4 hrs behind
My system is a single node DB using ASM.
How can I correct this anomaly, I have tried restarting the LISTENER but with no joy.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC0)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production
Start Date 29-APR-2014 15:16:44
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP ON
Listener Parameter File /oracle/product/11.2.0/db/network/admin/listener.ora
Listener Log File /oracle/diag/tnslsnr/mysvr_1/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.x.x)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "db1" has 1 instance(s).
Instance "db1", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[mysvr_1:/oracle]$sqlplus /nolog
SQL*Plus: Release 11.2.0.1.0 Production on Tue Apr 29 15:16:58 2014
Copyright (c) 1982, 2009, Oracle. All rights reserved.
SQL> conn user1/user1
Connected.
SQL> select to_char(sysdate,'dd/mm/yyyy hh24:mi:ss') from dual;
TO_CHAR(SYSDATE,'DD/MM/YYYYHH24:MI:SS')
--------------------------------------------------------------------------------
29/04/2014 15:17:32
SQL>
SQL> conn user1/user1@db1
Connected.
SQL> select to_char(sysdate,'dd/mm/yyyy hh24:mi:ss') from dual;
TO_CHAR(SYSDATE,'DD/MM/YYYYHH24:MI:SS')
--------------------------------------------------------------------------------
29/04/2014 11:17:56
SQL> !date
Tue Apr 29 15:20:26 GMT+02:00 2014