current timestamp shows wrong time

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Damir - 28 Mar 2008 10:35 GMT

I have a situation on a DB server where the "current timestamp" command
shows the actual system time offset by one hour, which has never been
noticed before?!?
The DB2 is V9.1 (FP03), running on AIX 5.3.
System timezone is offset by one hour to GMT, but this shouldn't cause such
behavior.

# echo $TZ
NFT-1DFT,M3.5.0,M10.5.0

# db2 "select current timestamp from sysibm.sysdummy1"
1
--------------------------
2008-03-28-11.21.07.753817
1 record(s) selected.

# date
Fri 28 Mar 2008 10:21:08

Any ideas on this one?

Regards,
Damir

Reply to this Message

Serge Rielau - 28 Mar 2008 12:10 GMT

> I have a situation on a DB server where the "current timestamp" command
> shows the actual system time offset by one hour, which has never been
[quoted text clipped - 16 lines]
>
> Any ideas on this one?

DST Daylight Savings Time

Signature

Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

Reply to this Message

Paul Peters - 28 Mar 2008 12:46 GMT

>> I have a situation on a DB server where the "current timestamp" command
>> shows the actual system time offset by one hour, which has never been
[quoted text clipped - 17 lines]
>> Any ideas on this one?
> DST Daylight Savings Time

We had the same problem on our AIX 5.3 servers. db2 v9.1 fp2 and 4. Since
Fri March 28th 02:00 the summertime is active on the instance of db2.
(current timezone changes then from 1 to 2). That's 2 days to early. So all
current timestamps are wrong. We could change the timestamp to yesterday and
then back to today. Then the time is correct. But what's happening on Sunday
then when the real summetime in Europe starts ?

We opened a Sev 1 PMR for this unexpected problem.

Paul

Reply to this Message

Serge Rielau - 28 Mar 2008 13:29 GMT

>>> I have a situation on a DB server where the "current timestamp" command
>>> shows the actual system time offset by one hour, which has never been
[quoted text clipped - 26 lines]
>
> We opened a Sev 1 PMR for this unexpected problem.

Presumably with AIX?
PS: Which country are you? Germany switched on Easter Sunday (I thought)

Signature

Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

Reply to this Message

Damir - 28 Mar 2008 14:02 GMT

...

>> We had the same problem on our AIX 5.3 servers. db2 v9.1 fp2 and 4. Since
>> Fri March 28th 02:00 the summertime is active on the instance of db2.
[quoted text clipped - 6 lines]
> Presumably with AIX?
> PS: Which country are you? Germany switched on Easter Sunday (I thought)

Here is my situation in more detail (on more different servers):
1. AIX 5.3_TL07, DB2 V9_FP03, current timezone = 2
2. AIX 5.3_TL07, DB2 V9_FP00, current timezone = 2
3. AIX 5.2_TL09, DB2 V9_FP02, current timezone = 1

It seems as though DB2 has a problem with AIX 5.3, since it works as
expected with AIX 5.2 ?!

Regards,
Damir

Reply to this Message

idenentjes@hotmail.com - 08 Apr 2008 09:12 GMT

Does anyone know if this is a real problem ? Is there indeed a
timezone-related bug in DB2 v9 on AIX 5.3 ?

Reply to this Message

juraj.hrapko@gmail.com - 08 Apr 2008 15:11 GMT

I think, that the timestamp generated from OS. Does your timestamp
shows different time than your OS ?
On Apr 8, 10:12 am, idenent...@hotmail.com wrote:

> Does anyone know if this is a real problem ? Is there indeed a
> timezone-related bug in DB2 v9 on AIX 5.3 ?

Reply to this Message

Paul Peters - 28 Mar 2008 14:03 GMT

>> We opened a Sev 1 PMR for this unexpected problem.
> Presumably with AIX?
> PS: Which country are you? Germany switched on Easter Sunday (I thought)

With AIX. : I'm coming from the Netherlands. Europe is switching on next
Sunday (March 30th)

Reply to this Message