DB2 LUW v8.2 FP 14 RHAS 2.1
Regarding DST:
My OS and java were successfully patched for DST, but the DB2 instance
was never bounced.
The OS returns the correct time, but a 'values current time' in DB2 is
an hour behind. If the OS is correct, shouldn't DB2 also be correct?
To fix it, do I only need to bounce the DB2 instance so that it sees the
correct time from the OS? Will anything else break? Recommendations?
TIA
aj
Jonathan Leffler - 15 Mar 2007 08:40 GMT
> DB2 LUW v8.2 FP 14 RHAS 2.1
>
[quoted text clipped - 4 lines]
> The OS returns the correct time, but a 'values current time' in DB2 is
> an hour behind. If the OS is correct, shouldn't DB2 also be correct?
Only if it is restarted so it re-reads the DST files.
> To fix it, do I only need to bounce the DB2 instance so that it sees the
> correct time from the OS? Will anything else break? Recommendations?
Yes. No.
Bounce DB2.
(OK: I'm applying the rules that apply to IDS - but I'd be surprised if
they differ for DB2).

Signature
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/
Ian - 18 Mar 2007 23:00 GMT
> DB2 LUW v8.2 FP 14 RHAS 2.1
>
[quoted text clipped - 7 lines]
> To fix it, do I only need to bounce the DB2 instance so that it sees the
> correct time from the OS? Will anything else break? Recommendations?
Didn't you reboot after applying the DST patches? Generally that's
required, because all processes need to be restarted in order to "pick
up" the changes to the timezone file.
aj - 20 Mar 2007 21:52 GMT
>> DB2 LUW v8.2 FP 14 RHAS 2.1
>>
[quoted text clipped - 9 lines]
> required, because all processes need to be restarted in order to "pick
> up" the changes to the timezone file.
No, I did not reboot the linux server, and the OS picked up the changes
just fine. I guess my sysadmin just restarted all relevant
services/processes...
As an aside: I bounced the DB2 instance last weekend, and DB2 picked
up DST just fine...
thanks
aj