The way I understand to protocal, the time shifts are not large jumps but
instead small changes for a period of time to match up the times. Plus
once the times are in sync, the daemon checks quite often for changes and
so only needs to make small changes. When a system first boots (or you
start xntp via /sbin/init.d/xntpd start) it first runs ntpdate which will
do a large jump.
if the two dates are to far out of range, xnpt will not try to sync. this
helps avoid the issue you fear below.
What I would do is check how far apart the two dates are (xntp server and
local system) and adjust the time manually to be within a couple of
seconds. Then I would start xntpd using the init.d startup command or
using sysman.
And you can do this off hours (non-peak) without issues.
>----- Original Messhage -----
>From: "Paul LaMadeleine" <plamadeleine_at_lightbridge.com>
>To: "leroux ludovic" <leroux_ludovic_at_netcourrier.com>
>Sent: Wednesday, February 27, 2002 5:58 PM
>Subject: Re: xntp and oracle?
>
>
> > We run xntpd on all our production servers without an issue. These range
> > from oracle/sybase data base servers to web servers on the unix side and
> > RDB database servers on the VMS side.
> >
> >
> >
> > At 05:48 PM 2/27/02 +0100, you wrote:
> > >do you think that it is dangerous to install xntp on a server with
>oracle?
> > >I think that the time and date isn't important with oracle but ...do you
> > >have install
> > >it with oracle and do you have some problems ?
> > >thanks
> >
Received on Fri Mar 01 2002 - 09:11:17 NZDT