DB2 - Problembeschreibung
Problem IC92158 | Status: Geschlossen |
TIMESTAMPS MAY NOT REFLECT DAYLIGHT SAVINGS TIME CHANGES IN CERTAIN SITUATIONS | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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 across 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 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 effect, causing them to be an hour ahead of the correct value. In certainly 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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description Above. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version V10.1 Fix Pack 3. * **************************************************************** | |
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. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in Version V10.1 Fix Pack 3. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC95167 IC96667 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 07.05.2013 29.08.2014 29.08.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |