|
Problem IT14856
|
Status: Closed |
DATABASE CAN REPORT INCORRECT TIME WITH NONE STANDARD TIME CHANGE LIKE CHANGES IN TIMEZONES |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
After non standard timezone changes in operating system DB2
might show incorrect time.
Output for "values current timezone" and "values current time"
might differ from
operating system returned with value. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 UDB Version 10.5 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 10.5 FixPack 7. *
**************************************************************** |
| Local Fix: |
setting TZ="UTC-INTEGER_OFFSET" inside ~/sqllib/userprofile and
restarting instance, where "INTEGER_OFFSET" corresponds to local
time zone |
| Solution |
Problem was first fixed in DB2 UDB Version 10.5 FixPack 7. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.04.2016
20.04.2016
20.04.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
