Solaris Daylight Saving Time (DST) Update (Aug 2008, Oct 2008, Mar-Apr 2009, Jun 2009, Aug 2009, Sep 2009, Oct 2009) |
|
| Category : | Availability | | Release Phase : | Resolved | | Bug Id : | 6542933, 6597032, 6606060, 6636785, 664589, 6674462, 6706537, 6723137, 6757452, 6764127, 6798406, 6821000, 6826916, 6828929, 6832623, 6843121, 6847404, 6850807, 6862458, 6872051, 6877621
| | Product : | Solaris 8 Operating System, Solaris 9 Operating System, Solaris 10 Operating System
| | Date of Resolved Release : | 07-Mar-2008
|
Solaris Daylight Saving Time (DST) Update (Aug 2008, Oct 2008, Mar-Apr 2009, Jun 2009, Aug 2009, Sep 2009, Oct 2009) 1. Impact
This Sun Alert contains updated patch revision levels to those
originally listed in Sun Alert 201521 (formerly Sun Alert 103044).
The original patch IDs have not changed for Solaris 8 and 9, and newer
revisions are now available. The latest patch IDs for Solaris 10 are
now listed in "Contributing Factors" and "Resolution" sections below.
Daylight
Saving Time (DST) and time zone definition changes occur in different
countries around the world on a regular basis. This Sun Alert will be
used to track ongoing daylight saving and timezone changes for Solaris.
As these changes come into
effect in each country, failure to implement the listed updates may
cause inaccurate date and time which could lead to unpredictable
results, depending upon usage.
BugID CR 6542933: update zoneinfo timezones to 2007f (Mongolia,
New Zealand, Indiana, etc)
February 8, 2007 - Mongolia has
chosen not to move to Summer Time (Daylight Saving Time) commencing
2007. Previously, each year the clock advanced one hour earlier during
the summer.
March 11, 2007 - Pulaski
County, Indiana, is switching from CST/CDT to EST/EDT which means a
2-hour change on March 11 2007. This requires a new Zone:
America/Indiana/Winamac.
April 30, 2007 - New Zealand
has decided to extend the daylight savings period to 27 weeks. Clocks
will go forward an hour a week earlier than usual - on the last Sunday
in September - and back an hour on the first Sunday in April instead of
the third Sunday in March. Daylight saving for 2007-08 will start at
2a.m. on 30 September 2007 and end at 3a.m. on 6 April 2008.
BugID CR 6597032: Update
zoneinfo timezones to 2007g (South Australia, Indiana, Egypt) - Egypt has changed the ending
date of DST. DST ended on September 7 in 2007.
- Daviess, Dubous, Knox, Martin,
and Pike Counties, Indiana, switch from central to eastern time in
November. This results in a zone split, and a new entry
America/Tell_City is created for Perry County, which does not switch
zones in November.
- South Australia, Tasmania,
Victoria, and New South Wales are changing their DST rules effective in
2008. DST will end the first Sunday in April at 03:00 and start the
first Sunday in October at 03:00. Lord Howe Island has a similar
change.
BugID CR 6606060: Update
zoneinfo timezones 2007h (Brazil, Egypt, Iran, Gaza, Venezuela) - Brazil observes DST from
2007-10-14 00:00 to 2008-02-17 00:00. - Iran will resume DST from 2008. - Venezuela is currently planning
to change time zones on January 1 2008, to 04:30.
BugID CR 6636785: Update
zoneinfo timezones to 2007j (Venezuela, Cuba, Syria) - Venezuela had decided to change
their clocks on December 9 at 03:00, instead of January 1 at 00:00 as
first thought. - Cuba will end DST one week
earlier - on the last Sunday of October. - Syria winter local time will be
observed at midnight on Thursday November 1 2007, and the clocks
will be put back 1 hour.
BugID CR 6645893: Update
zoneinfo timezones to 2007k (Argentina, Jan Mayen) - Argentina re-adoption of
daylight saving time to commence at the start of the day Sunday
December 30, and finishing at the start of the day Sunday March 16. BugID CR 6674462: Update zoneinfo timezones 2008b (Chile, Argentina, Cuba, Iraq, Syria)
- Chile extends Daylight Time in three weeks. DST starts at Saturday,
March 29 (24:00 in America/Santiago, 22:00 in Pacific/Easter)
- The Province of San Luis in Argentina decided to go back to UTC-3 effective midnight Jan 20th 2008
- Cuba (from 2008 forward) starts DST at the third Sunday in March.
- Iraq abandons DST. - Syria switched (from 2008 forward) to start DST at the start of the first Friday in April and end DST at the start of Oct 1.
BugID CR 6706537: Update zoneinfo timezones to 2008c (Mongolia, Morocco, Pakistan)
- Choibalsan in Mongolia is now 8 hours off UCT.
- Morocco observes DST in 2008.
- Pakistan observes DST in 2008. BugID CR 6723137: Update zoneinfo timezones to 2008e (Brazil, Mauritius, Argentina)
- Mauritius observes DST 2008-2009. - Changes to reflect Brazilian time zone realignments
BugID CR 6757452: zoneinfo timezones 2008h (Brazil, Argentina, Palastine, Pakistan, etc.)
- Reflecting changes in Mauritius DST rule. - Morocco changes DST rules. - Gaza changes DST rules. - Pakistan changes the end of 2008 DST from Sep 1st to Nov 1st. - Argentina starts 2008 DST from 3rd Sunday. - Brazil starts 2008 DST from 2nd Sunday. - Update in the Maurituis DST transition hours. - Syria ends DST on Nov 1st.
BugID CR 6764127: update zoneinfo timezones to 2008i (Argentina)
- Changes to reflect the latest Argentina DST rules. BugID CR 6798406: update zoneinfo timezones to 2009c - Cuba started Daylight Saving Time beginning March 8th in 2009. BugID CR 6821000: update zoneinfo timezones to 2009d (Argentina, Morocco,
Tunisia, Syria)
- The Province of San Luis (Argentina) started DST from March 15th until the
second Saturday in October.
- Tunisia will not observe DST this year.
- Morocco will observe DST from 2009-06-01 to 2009-08-21.
- Syria will start DST on 2009-03-27 00:00 this year. BugID CR 6826916: update zoneinfo timezones to 2009e (Jordan, Palestine)
- Palestinian government decided to start Daylight Time on Thursday
night March 26 and continue until the night of 27 September 2009.
- Jordan is going to daylight saving time on the last Friday in March
since 2002.
BugID CR 6828929: update zoneinfo timezones to 2009f (Pakistan) - Pakistan plans to introduce DST from April 15, 2009 BugID CR 6832623: update zoneinfo timezones to 2009g (Egypt)
- Egypt ends DST on the last Thursday in September from 2009 and forward.
BugID CR 6843121: update zoneinfo timezones to 2009h (Jordan)
- The start of DST in Jordan from 2002 forward is changed from
0:00 on the last Friday of the month to 24:00 on the last Thursday.
BugID CR 6847404: update zoneinfo timezones to 2009i (Bangladesh)
- Bangladesh introduces daylight savings this year which will start
from June 19 midnight. The clock will go ahead 1 hour at that time. BugID CR 6850807: update zoneinfo timezones to 2009j (Bangladesh DST
starts earlier)
- Bangladesh started DST one hour eariler than expected in the
BugID/CR 6847404. BugID CR 6862458: update zoneinfo timezones to 2009k (Bangladesh,
Mauritius)
- Arbitrarily cut off Dhaka DST at end of 2009. Note that another
change will be needed once the real end date for DST in Dhaka is known.
- Change Mauritius to reflect that 2008-2009 DST experiment is not
repeated (and to change end of DST in 2009 from 2:00 standard time to
2:00 local time). BugID CR 6862458: update zoneinfo timezones to 2009l (Egypt)
- Egypt's DST will end at midnight, Aug 20th in 2009. BugID CR 6877621: update zoneinfo timezones to 2009m (Palestine, Samoa)
- Palestinian Council of Ministers announced that DST will end on
September 4, 2009.
- Samoa will start DST on the first Sunday of October 2009 and end on
the last Sunday of March 2010. BugID CR 6891724: update zoneinfo timezones to 2009o (Bangladesh,
Pakistan)
- Bangladesh continues DST in 2009.
- Pakistan will end DST on November 1st 2009 (and in future years)
BugID CR 6893824: update zoneinfo timezones to 2009p (Argentina)
- Argentina will not use DST in 2009-2010 BugID CR 6896172: update zoneinfo timezones to 2009q (Syria)
- Syria will revert back to winter (standard) time on midnight between
Thursday 2009-10-29 and Friday 2009-10-30.
- Introducing Asia/Novokuznetsk timezone.
2. Contributing Factors
These issues can occur in the
following releases: SPARC Platform:
x86 Platform:
Note: Solaris 8 entered EOSL Phase 2 on 1 April 2009. Entitlement to
patches developed on or after 1 April 2009 requires the purchase of the
Solaris 8
Vintage Patch Service. See Note in section 5 for more details.
3. Symptoms
Systems will experience
incorrect system time or date after timezone changes go into effect.
4. Workaround
There is no easy way
to avoid these issues. Attempts to change the TOD clock of the system
are temporary and will not resolve all the time zone issues resolved by
the patches listed in the Resolution section. It is advised that
updated patches are installed to resolve
the time zone changes and issues.
Binary relief for CR 6872051, 6877621, 6891724, 6893824 and 6896172 is available through
normal support channels.
5. Resolution
These issues are addressed in
the following releases: SPARC Platform:
x86 Platform:
Solution for the latest changes (BugID/CR 6872051, 6877621, 6891724, 6893824 and 6896172) are not included in the above patches (Please see the "Workaround" section).
Note: The READMEs of Solaris 8
patches developed on or after 1 April 2009 are available to all
customers. However, Solaris 8 entered EOSL Phase 2 on April 1, 2009 and
thus entitlement for these patches, including those that fix security
vulnerabilities, requires the purchase of the Solaris 8 Vintage Patch
Service. More information about the Solaris 8 Vintage Patch Service is
available at: http://www.sun.com/service/eosl/Solaris8.html
Solution for the changes below are not included in the above Solaris 8
patches. BugID/CRs 6847404, 6850807, 6862458, 6872051, 6877621, 6891724, 6893824, 6896172.
Note 1: Once these
patches are applied, at(1) jobs may not be scheduled correctly.
This will happen if both the
following conditions are present:
-
at(1) jobs have been
submitted before patch installation.
-
Those jobs will be executed
during the extended DST periods.
at(1) jobs which meet these two
conditions can be scheduled one hour later or earlier. Please run
atq(1) to see if jobs are scheduled correctly after patch installation.
If there are discrepancies,
remove jobs using atrm(1) and resubmit the jobs.
Note 2: Once these
patches are applied and the system rebooted, to complete the
installation of these changes, systems which are running CDE calendar
manager [dtcm(1)] or the CDE calendar server daemon [rpc.cmsd] will
find that some scheduled events in the extended/changed DST period are
incorrect by one hour.
This will happen under the
following conditions:
-
Events were created before
DST patch installation and reboot.
-
Those events were created
while the CDE calendar manager was using a time zone which has been
impacted by the changes described by this Sun Alert.
-
Those events were single
events scheduled for dates in the extended/changed DST periods, or
those events were recurring events for which the first instance of the
event is in the extended/changed DST period.
To address this issue, recreate
all single events in the affected time period and all recurring events
for which the first instance of the event is in the affected time
period.
Note 3: Those systems
which are not in one of the affected timezones and not using any
programs which switch to using one of the affected timezones will not
need these patches.
Note 4:
Information on
previous daylight saving and timezone changes for Solaris can be found
in Sun Alert 200097 (formerly Sun Alert 102775):
Note 5: Daylight saving and timezone information on
other Sun products can be found at:
This
Sun Alert notification is being provided to you on an "AS IS"
basis. This Sun Alert notification may contain information provided by
third parties. The issues described in this Sun Alert notification may
or may not impact your system(s). Sun makes no representations,
warranties, or guarantees as to the information contained herein. ANY
AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU
ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT
OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This
Sun Alert notification contains Sun proprietary and confidential
information. It is being provided to you pursuant to the provisions of
your agreement to purchase services from Sun, or, if you do not have
such an agreement, the Sun.com Terms of Use. This Sun Alert
notification may only be used for the purposes contemplated by these
agreements.
Copyright 2000-2009 Sun Microsystems, Inc., 4150 Network Circle, Santa
Clara, CA 95054 U.S.A. All rights reserved.Modification History07-Mar-2008: Created as the Update/Replacement for Sun Alert 201521 (formerly 103044)
19-Aug-2008: Updated BugIDs, Title, Impact, Contributing Factors, Resolution, and Patches
29-Oct-2008: Updated Impact (BugIDs 6723137, 6757452, 6764127) and Workaround section (for IDRs)
08-Dec-2008: Updated patches in Contributing Factors and Resolution sections 17-Mar-2009: Add BugID 6798406; updated Impact and Workaround sections 24-Mar-2009: Add BugID 6821000; updated Impact and Workaround sections 13-Apr-2009: Add BugIDs 6826916; 6828929; Updated Impact and Workaround sections 04-Jun-2009: Add BugIDs 6832623; 6843121, 6847404; Updated Impact, Contributing Factors, Workaround and Resolution 23-Jun-2009: Add BugID 6850807; Updated Impact, Workaround, Resolution sections 05-Aug-2009: Add BugID 6862458; Updated Impact, Workaround, Resolution sections 18-Aug-2009: Add BugID 6872051; Updated lmpact, Workaround, Resolution sections 08-Sep-2009: Add BugID 6877621; Updated lmpact, Workaround, Resolution sections 26-Oct-2009: Add BugIDs 6891724, 6893824; Updated lmpact, Workaround, Resolution sections 31-Oct-2009: Add BugID 6896172, Updated lmpact, Workaround, Resolution sections AttachmentsThis solution has no attachment
|
|
Login Required
You must login and have a valid contract to access Sun's Premium content which includes:
- Sun Alerts
- Bugs
- Patches
- Solutions
- White Papers
- Documentation
- Support Knowledge
Login Required
You must login and have a valid contract to access Sun's contracted features
|
Access Legend:
Sun Contracted Content
Sun Contracted Feature
|
Please make use of SunSolve Feedback application by selecting the floating [+] to provide feedback about this specific document.
|