|
Problem IC95167
|
Status: Closed |
TIMESTAMPS MAY NOT REFLECT DAYLIGHT SAVINGS TIME CHANGES IN CERTAIN SITUATIONS |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
In DB2 pureScale environments certain timestamps used by DB2 may
not accurately reflect the current "daylight savings time" (aka
"Summer Time") status if the DB2 member has been up during a
daylight savings time change. Not all timestamps are affected,
which can in certain scenarios lead to errors.
For example, if a DB2 pureScale instance is started in
mid-October and left running through to the end of North
American
Daylights Savings Time (currently the first weekend in
November), certain timestamps used by DB2 will still be
calculated as if Daylight Savings Time is in effect, causing
them
to be an hour ahead of the correct value.
In certain scenarios this can lead to objects that appear to
have been created in the future, leading to errors if an attempt
to alter the object is made before the "create" time has passed
(in other words, within an hour of object creation). This can
manifest in several ways, including SQL0204 errors when
accessing objects with incorrect creation times. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 1. *
**************************************************************** |
| Local Fix: |
When Daylight Savings Time has begun (Spring) or ended (Fall),
individual DB2 pureScale members should be stopped and
restarted. After restart the member will return correct
timestamps. Once all members have been restarted the instance
is not exposed to this issue until the next Daylight Savings
Time change. Member restarts can be staggered so that overall
availability is not impacted. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.5 Fix Pack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.08.2013
21.08.2014
21.08.2014 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
