RE: RAC time clocks (sysdate)

From: Jesse, Rich <Rich.Jesse_at_qtiworld.com>
Date: Thu, 10 Jul 2003 13:25:52 -0700
Message-ID: <F001.005C44C3.20030710131925@fatcity.com>

Hey Matt!

I thought that it was a bit of proper manners to avoid hitting the public stratum-1 servers unless you were planning on being a public stratum-2, just to avoid overloading the stratum-1s.

Thoughts?
Rich

Rich Jesse
System/Database Administrator

Quad/Tech Inc.
A Subsidiary of Quad/Graphics

Sussex, Wisconsin USA
414-566-7633 phone
[EMAIL PROTECTED]
www.qtiworld.com

-----Original Message-----
Sent: Thursday, July 10, 2003 3:29 PM
To: Multiple recipients of list ORACLE-L

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.

The 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.

Thanks,
Matt
--

Please see the official ORACLE-L FAQ: http://www.orafaq.net
--

Author: Jesse, Rich
INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Thu Jul 10 2003 - 15:25:52 CDT