From: jreed@appliedtheory.com
Date: Thu Oct 03 2002 - 10:04:24 EDT
I had reported a problem in TCR v5.1a/Oracle 9iRAC where when DBAs enqueued
records into database, time was always 2 days in the future. Turns out that
after upgrading Oracle, rebuilding some oracle internals as part of upgrade,
and stopped/restarted database, some combination of these changes reset
the time/date info and resolved the problem
A few people did respond, suggestions were as follows:
>From Pat O'Brien:
check your timezone settings, or locales to see if they are different.
>From Raul Sossa S.:
Review the following things:
1. Find by "clock" on this pdf file, is it your problem ?
2. Are your both nodes already synchronize with NTP Daemon,
how far are they each other?.
3. Are both oracle instances answering the same behaviour, or only one
in one node ?
4. Do you have oracle9i RACK second release ?
5. If your dba type a "SELECT SYSDATE FROM DUAL;" connected as "sysdba"
does it says a right answer, comparing it with the other oracle instance?
Are this responses similar to the operating system "date" instruction?
Try to detect if the problem is in the oracle9i site or in the
OS side, if your think it is in the os side you might consider
applying this patch. (a patch he attached)
Thanks to those folks!
JR
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:55 EDT