Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Neil Truby planned to correct the clocks on two HP-UX 10.20 production servers, one 5 minutes fast and one 5 slow, and asked about Informix problems. Madison Pruet said trouble was unlikely unless using Enterprise Replication. Derek Runstadler advised moving the slow clock forward, since log timestamps going back could endanger logical recovery. Steve Hemminger noted Solaris date -a slews the clock gradually. No final outcome.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Neil Truby — — source: Informix-list mailing list archive (1991-1998)
I'm intending to update the time on two production servers (K460 HP-UX
10.20). One's 5 minutes fast and one's 5 minutes slow.
Does anyone know of any problems this might cause to the Informix servers
running on each?
thanks
Neil
↪ replying to Neil Truby
Madison Pruet — — source: Informix-list mailing list archive (1991-1998)
Generally you wouldn't run into problems unless using Enterprise
Replication. Of course the value of "current" would be different on each of
them.
Neil Truby wrote:
> I'm intending to update the time on two production servers (K460 HP-UX
> 10.20). One's 5 minutes fast and one's 5 minutes slow.
>
> Does anyone know of any problems this might cause to the Informix servers
> running on each?
>
> thanks
>
> Neil
↪ replying to Neil Truby
Derek Runstadler — — source: Informix-list mailing list archive (1991-1998)
In article <7ih39n$f3f$1@taliesin.netcom.net.uk>,
"Neil Truby" <ntruby@netcomuk.co.uk> wrote:
> I'm intending to update the time on two production servers (K460 HP-UX
> 10.20). One's 5 minutes fast and one's 5 minutes slow.
>
> Does anyone know of any problems this might cause to the Informix
servers
> running on each?
>
> thanks
>
> Neil
>
>
If you can't shut down the instances for 5 minutes to
sync the times, I would make the slower machine 5 minutes
faster rather than making the faster machine 5 minutes slower.
It seems to me that "if" you needed to do a restore and
logical recovery, the log time stamps going back in time may
cause the logical recovery to be in jeopardy.
--
Derek Runstadler
--== Sent via Deja.com http://www.deja.com/ ==--
---Share what you know. Learn what you don't.---
↪ replying to Derek Runstadler
Steve Hemminger — — source: Informix-list mailing list archive (1991-1998)
On Solaris, there is an adjust flag to the date command which will
slowly speed up/slow down and this should cause the least impact on
the server since the same number of clock events will get scheduled.
man date
...
-a [-]sss.fff
Slowly adjust the time by sss.fff seconds (fff
represents fractions of a second). This adjust-
ment can be positive or negative. The system's
clock will be sped up or slowed down until it
has drifted by the number of seconds specified.
Your privacy choices
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.