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.
Juan Manuel Hernandez del Olmo asked whether changing the server clock by several hours would harm IDS, e.g. the logical logs. smooth1 said Informix uses an internal timestamp counter, so no problem. Rob Wilson recalled Y2K tests needing the engine down for date changes and advised testing first. Art S. Kagel said with USEOSTIME 0 CURRENT may briefly return the old time; shut the engine down for changes beyond a few seconds.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hello everybody.
I would like to know if there would be any problem if I change the time of my informix server. I am worried about the effect of this change (several hours) on the IDS. For example, the impact of this over the logical logs.
Thanks in advance.
jhernandez@geuropa.com
↪ replying to =?ISO-8859-1?Q?Juan=20Manuel=20Hern=E1ndez=20del=20Olmo?=
smooth1 — — source: Informix-list mailing list archive (1991-1998)
There should be no problems as Informix using an internal
timestamp counter.
Juan Manuel Hern'ndez del Olmo wrote in message
<8rae2f$acu$1@news.xmission.com>...
>
>Hello everybody.
>
>I would like to know if there would be any problem if I change the time of
my informix server. I am worried about the effect of this change (several
hours) on the IDS. For example, the impact of this over the logical logs.
>
>Thanks in advance.
>jhernandez@geuropa.com
>
>
↪ replying to smooth1
Rob Wilson — — source: Informix-list mailing list archive (1991-1998)
I do remember running into problems during Y2K testing... You had to
bring down Informix when you were changing dates. Of course, we were
changing months at a time and not hours...
Informix is using internal timestamps so that is not what was causing
the problem. I would suggest using your test instance (if you have
one) and resetting its clock while Informix is running. I recommend a
good backup first, though.
On Tue, 3 Oct 2000 23:32:34 +0100, "smooth1" <smooth1@iclway.co.uk>
wrote:
>
>There should be no problems as Informix using an internal
>timestamp counter.
>
>Juan Manuel Hern'ndez del Olmo wrote in message
><8rae2f$acu$1@news.xmission.com>...
>>
>>Hello everybody.
>>
>>I would like to know if there would be any problem if I change the time of
>my informix server. I am worried about the effect of this change (several
>hours) on the IDS. For example, the impact of this over the logical logs.
>>
>>Thanks in advance.
>>jhernandez@geuropa.com
>>
>>
>
>
--
Rob Wilson
rwilson@ntsource.com
↪ replying to =?ISO-8859-1?Q?Juan=20Manuel=20Hern=E1ndez=20del=20Olmo?=
Art S. Kagel — — source: Informix-list mailing list archive (1991-1998)
If you ONCONFIG file has USEOSTIME 0 there may be a short period until the
engine queries the system again to determine the system time when CURRENT
and similar functions will return the old time (or a time derived from it)
as without USEOSTIME set to 1 the engine only queries the actual system
time periodically and interpolates in between.
It is best to shutdown the engine when you change the system clock by
anything more than a few seconds.
Art S. Kagel
Juan Manuel Hernández del Olmo wrote:
>
> Hello everybody.
>
> I would like to know if there would be any problem if I change the time of my informix server. I am worried about the effect of this change (several hours) on the IDS. For example, the impact of this over the logical logs.
>
> Thanks in advance.
> jhernandez@geuropa.com
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.