If I select sysdate directly on the 2nd instance server, it's also correct.Then why is this an Oracle problem & not a remote client problem?
Only if I connect to the 2nd instance remotely, then the time returns wrong.
z3k2 wrote:Some thoughts:
I have a RAC with two instances. SYSDATE returns correct on one instance (EDT) but wrong on the other (PDT) with 3 hour difference. The two servers time are the same (EDT) and they are located in Toronto. If I select sysdate directly on the 2nd instance server, it's also correct. Only if I connect to the 2nd instance remotely, then the time returns wrong. Any thought?
Franck Pachot wrote:I tried everything which were suggested in this post as well as from other websites. Here is the scenario:
If OS time was the same, then the TZ environment variable set when the instance was started was probably different.
Maybe your instance was started from a shell that had a bad TZ variable.
If problem happen again, you can check it with:
connect / as sysdba
var s varchar2(4000);
exec dbms_system.get_env('TZ', :s);