Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: RAC time clocks (sysdate)

RE: RAC time clocks (sysdate)

From: Matthew Zito <>
Date: Thu, 10 Jul 2003 12:36:34 -0700
Message-ID: <>

<FONT face=Arial color=#0000ff

size=2>Beware, NTP can be a complicated critter to get working in a proper fashion.  The best way to configure your NTP is to have one or two local stratum 2 or stratum 3 servers that all of your nodes sync off of (a good choice for these servers are servers that do other low-load internal services like mail relay or DNS).  Those servers should each be configured with two unique stratum 1 or 2 servers and then set up to peer off of each other.  Then, point your database servers at your stratum 2 servers.  If your servers are too far out of sync with the rest of the world, NTP won't change the clocks instantaneously, but will gradually "drift" your clocks into sync.  If you want to rush the process, stop the ntpd process, use ntpdate to set the clock one time, and then restart ntp.  The drift should be small enough that will immediately maintain synchronization.
<FONT face=Arial color=#0000ff

above config is a little bit over-engineered if you only have a few hosts, but if you don't already have a global time management system configured, now is the time (no pun intended) to do it - its one of those things that should be required for any infrastructure.  Properly synchronized time makes things like auditing, monitoring, and general sanity an order of magnitude easier.  The above system will easily scale to up to a few hundred hosts and basically insures that the time will be consistent across the infrastructure as a whole.  The other nice thing about NTP is that its an interesting protocol, for those who care about such things, since it actually makes a distinct effort to take network latency and so-such into consideration when setting the time.
<FONT face=Arial color=#0000ff

<FONT face=Arial color=#0000ff

<FONT face=Arial color=#0000ff

--Matthew ZitoGridApp SystemsEmail:
[EMAIL PROTECTED]Cell: 646-220-3551Phone: 212-358-8211 x 359<A href="">

style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">   

  face=Tahoma size=2>-----Original Message-----From:   [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick   WagnerSent: Thursday, July 10, 2003 1:10 PMTo: Multiple   recipients of list ORACLE-LSubject: RE: RAC time clocks   (sysdate)
  <FONT face=Arial color=#0000ff
  <FONT face=Tahoma
  size=2>-----Original Message-----From: Jamadagni, Rajendra   [mailto:[EMAIL PROTECTED]Sent: Thursday, July 10, 2003   10:40 AMTo: Multiple recipients of list ORACLE-LSubject:   RE: RAC time clocks (sysdate)
  Our sysadmins use ntp or something like that .   Raj <FONT

  Rajendra dot Jamadagni at nospamespn dot com <FONT   size=2>All Views expressed in this email are strictly personal.   QOTD: Any clod can have facts, having an opinion is an art   !
  -----Original Message----- From: Nick   Wagner [<A
  href="mailto:[EMAIL PROTECTED]">mailto:[EMAIL PROTECTED]]   Sent: Thursday, July 10, 2003 1:09 PM <FONT   size=2>To: Multiple recipients of list ORACLE-L <FONT   size=2>Subject: RAC time clocks (sysdate)   In a RAC environment, what is the best way to synchronize the   time clocks on the nodes?   It seams I came across a case where   select sysdate from dual; produced two different values.   Thanks!
  Nick Received on Thu Jul 10 2003 - 14:36:34 CDT

Original text of this message