Time flies

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

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

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

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.