Begin Tab Sub Links

Software

last updated on: 2008-09-09



Solaris


Trusted Solaris (TS)

Products/versions affected:
  • TS 8 2/04
  • TS 8 HW 7/03
  • TS 8 HW 12/02
  • TS 8 HW 4/01
  • TS 8 (FCS)
  • TS 7
  • TS 2.5.1

 

Each version of TS requires its own DST patch.

 

  • TS 8 2/04:
    • libc (sparc): 125226-01, libc (x86): 125227-01, zoneinfo (sparc): 125228-01, zoneinfo (x86): 125229-01
  • TS 8 HW 7/03:
    • libc (sparc): 125230-01, libc (x86): 125231-01, zoneinfo (sparc): 125232-01, zoneinfo (x86): 125233-01
  • TS 8 HW 12/02:
    • libc (sparc): 125234-01, libc (x86): 125235-01, zoneinfo (sparc): 125236-01, zoneinfo (x86): 125237-01
  • TS 8 HW 4/01:
    • libc (sparc): 125238-01, zoneinfo (sparc): 125240-01

 

TS 2.5.1, 7 and 8 (FCS) are in Phase 2 of Vintage Support. See Vintage Solaris Feature Article

Solaris Security Toolkit

The Toolkit only uses time information available from the Solaris instance installed on the system and, is supported on Solaris 8, 9 and 10.


Java (SE) JRE/JDK

For information about how daylight savings time affects the Java SE platform, see Timezones, Daylight Savings Time, and the Sun TZUpdater Tool for the Java Runtime Environment

Java SE & Solaris (Java Applications embedded in Solaris)




Access Manager, Access Manager Agents, Federation Manager

All supported Access Manager (6.1, 6.2, 6.3, 7.0, 7.1), Access Manager Agents (2.1 and 2.2) and Federation Manager (7.0) are affected. The JDK versions being used which will need to be updated to a Java version with the DST changes are:
  • JDK 1.5
  • JDK 1.4
  • JDK 1.3
All the products use the time information from the JDK or the OS. There are no fixes expected in these products. The fix will be done by applying the patches from the dependent components JDK and OS. Customer actions needed:
  • Apply patches for OS and JDK.
  • Application restart is required after applying the JDK patch.
  • Restart the container in which Access Manager, Agents or Federation Manager are running.
Customer impacts if changes not applied:
  • Time functions will be impacted. Access Manager and Agents have few functionalities where time functions are used. They will misbehave to reflect the old DST time if changes are not applied.



Application Server

Products/versions affected:
  • AS 9.0 UR1 Patch1
    • Uses JDK to obtain DST, JDKs supported: 1.5.x, 6.0
    • OS supported - Solaris 10 and 9 on SPARC and x86, 64bit Solaris 10 Operating System (on SPARC), Microsoft Windows 2000 Advanced Server, Microsoft Windows Server 2003, Microsoft Windows XP, Red Hat Enterprise Linux 3.0 and 4.0
  • AS 9.0, AS 9.0 UR1
    • Uses JDK to obtain DST, JDKs supported: 1.5.x
    • OS supported - Solaris 10 and 9 on SPARC and x86, 64bit Solaris 10 Operating System (on SPARC), Microsoft Windows 2000 Advanced Server, Microsoft Windows Server 2003, Microsoft Windows XP, Red Hat Enterprise Linux 3.0 and 4.0
  • AS 8.0, AS 8.1, AS 8.2
    • Uses JRE and OS to obtain DST
    • JDKs supported: 1.4.x, 1.5.x
    • Requires OS patches and Java upgrades to be installed
    • OS supported - Solaris 10, 9, and 8 on SPARC, Solaris 10 and 9 on x86, Red Hat Enterprise Linux 2.1 (Update 2) and 3 (Update 1), Microsoft Windows 2000 Advanced Server SP4, Microsoft Windows Server 2003.
  • AS 7.0, AS 7.1
    • Uses JRE and OS to obtain DST
    • JDKs supported: 1.4.x
    • Requires OS patches and Java upgrades to be installed
    • OS supported - Solaris 9 and 8 on SPARC, Solaris 9 on x86, Red Hat Enterprise Linux AS 2.1 and 3, Microsoft Windows XP Professional, Windows 2000 Professional, and Windows 2000 Advanced Server
  • AS 6.5 (EOL - Not Supported)
    • Uses JRE and OS to obtain DST
    • JDKs supported: 1.2.x
    • Requires OS patches and Java upgrades to be installed
    • OS supported - Solaris 8 and 2.6, Microsoft Windows NT 4.0 SP6a and Windows 2000 SP2, Professional, Server, and Advanced Server Editions, AIX 4.3.x, HP-UX 11.x
Application restart required for all products. Customer actions needed:
  • Shutdown server(s) by using Admin console or CLI
  • Install all necessary OS patches to address the DST issue in the OS
  • Refer to Java DST Information.
  • Restart the server(s)
NOTE:
  • AS8.1Patch 13 will contain JVM 1.5.0.6 that has the DST fix. To avoid vulnerability issues, Customers are advised to apply the Sun Alert 102760 for Java versions or use the tzupdater tool.
  • Java 5.0u6 has the DST fixes for USA only. Customers outside the USA, will need a later Java version (5.0u8 or later) OR use the tzupdater tool to move the 5.0u6 instance to the latest TZ information.



C++ Development Environment (Rogue Wave library)

  • The C++ development environment has a library from Rogue Wave.
  • SunAlert 102754 released



Calendar Server

Products/versions affected:

DST Updates:
  • Refer to Sun Alert 103058
  • No patches to be provided for versions 6.1 or lower.
2007 U.S., Canada, Western Australia, Bahamas:
  • Calendar Server 5.1.1, 6.0, 6.1 and 6.2
    • Uses application specific file (timezones.ics) for DST
      • For 5.1.1, open a support call to get a latest hotfix 5.1.1hf1.28
      • For 6.x, refer to Sun Alert 102792
        • North/South America: 116577-40 (Solaris Sparc), 116578-40 (Solaris x86), 117851-40 (Linux)
          Note: Refer to http://docs.sun.com/app/docs/doc/819-2433/6n4nlfjt5?a=view for Administering Calendar Server Time Zones.
        • Australia: 116577-41 (Solaris Sparc), 116578-41 (Solaris x86), 117851-41 (Linux)
        • For Windows and HPUX, open a support call to obtain the timezones.ics file.
    • OS supported: Solaris Sparc/x86 (8,9,10), Windows (2000 Advanced Server, SP4, 2003 Enterprise Server, XP SP1 and SP2), HP-UX 11i, Red Hat Linux (2.1,3.0)
    • Note: Date/Time is converted and stored in GMT. To date, a method has not been found to determine GMT offset used for the conversion, after an event has been created.
      After updating the timezone information file, pre-existing events scheduled for the days between the old and new change-over dates will show a one hour discrepancy. To address these particular events, customers can edit the single events and the instances of recurring series that fall in the above time period to reflect the correct time. In the case of events with attendees, the organizer can edit the events and that change will be reflected in an attendee's calendar.
Customer actions needed:
  • Install applicable patch as noted or replace timezones.ics file (Windows/HPUX) and restart. Refer to Sun Alert 102792
  • Restart application.
Customer impacts if changes not applied:
  • Events created in the days between new daylight switchover and old daylight switchover will be off by one hour in the affected timezones.



Common Desktop Environment (CDE)

  • The CDE and OpenWindows calendar manager and command line utilities are impacted. They use the timezone information provided by the OS. See Sun Alert 234461. No specific CDE or OpenWindows patches are required for DST compliance.
  • Customer actions needed: Apply patches for the OS as described in Sun Alert 234461. After applying the patch, pre-existing events scheduled for the days between the old and new change-over dates may show a one hour discrepancy. To address these problem events, customers should review all single events in the above time period and all recurring events that have at least one instance falling into the above time period.



Configuration and Service Tracker (CST)

Products/versions affected:
  • CST - All versions affected
    • Uses Java (Middleware server component and server GUI) and Sun OS to obtain DST
    • Java supported: 1.2 or later
    • OS supported: Solaris Sparc (10,9,8,7 and 2.6)
Customer actions needed:
  • Middleware (Server) host:
  • Agent host:
    • Stop the CST Agent
    • Apply Solaris OS Patches
    • Restart the Agent applying the upgrades.
Customer impacts if OS changes not applied:
  • Middleware (Server) and Agent hosts
    • Incorrect availability reports
    • Incorrect outage calculation
    • Incorrect timestamp for generated events
    • Incorrect timestamp on Cause Codes
    • Incorrect timestamp in log files
Customer impacts if Java updates are not applied:
  • On Middleware (Server) host:
    • Incorrect time will be shown on the GUI
  • On Agent Host:
    • No impact, as Java is not used in the Agent component of CST



Content Delivery Server

Two major versions of the CDS are currently supported and effected. All minor releases in the form of Product Updates (PUs) are effected. As CDS itself is only indirectly affected, no specific bugs or patches related to CDS are required.

 

Oracle Note: CDS does not use the TSTZ or TSLTZ types or the TZ_OFFSET function so no Oracle updates are required for either Oracle 9.x or 10.g.

 

Products/versions affected:
  • Content Delivery Server 4.0 (IR1 through IR10)
    • Requires Solaris and JDK upgrades to avoid issues
    • OS supported: Solaris 9 SPARC, HP-UX 11i
    • Oracle Database 9i, version 9.0.1 or later
    • Requires JDK fixes for:
      • Application Server Edition 7 Update 3
      • BEA WebLogic Server 7.0
      • JDK Versions: Weblogic: 1.3.1_10, Application Server 1.4.2_04
  • Content Delivery Server 5.0, 5.0PU1
    • Requires Solaris and JDK upgrades to avoid issues
    • OS supported: Solaris 9, 10 SPARC, HP-UX 11i
    • Oracle Database 9i, version 9.2.0.6 or later, Standard or Enterprise Edition
    • Oracle Database 10g Release 1 (10.1.0.2) or later, Standard or Enterprise Edition
    • Requires JDK fixes for:
      • Application Server Standard/Enterprise Edition 8.1
      • BEA WebLogic Server 8.1
Customer actions needed:
  • Stop server
  • Upgrade Java in CDS and Application Server/Weblogic
  • Apply changes to Oracle as noted above
  • Install all necessary OS patches to address the DST issue in the OS
  • Restart the server
Customer impacts if changes not applied:
  • Message and log timestamps will be inaccurate.
  • Some time-based pricing plans will be off by one hour in the effected timezones.
  • Billing forwarded to an external system, may have times/dates be off by one hour.



Developer Products

Products/versions affected: Customer actions needed:
  • Application restart is required after applying the Java, OS. C++ and FW patches as indicated in the matrix.
    • For OS: Follow instructions in the OS patch README
    • For FW: Follow instructions in the Firmware patch README
    • For Java: Follow instructions in the Java SE installation instructions
    • For C++: Follow instructions in the C++ patch README:
      • If an application does not use RW Tools.h++ and links to the shared (.so) version of Solaris system libraries, halt the application, apply the appropriate Solaris patches, and restart the application. The application will then have the correct DST adjustments.
      • If an application uses the shared version of librwtool, apply the Sun C++ compiler patch, then update all installations of the application with the new version of librwtool.so.2. Also apply the appropriate Solaris patch to all systems.
      • If an application links the static librwtool.a, apply the Sun C++ compiler patch, re-link the application, and update all installations of the application. Also apply the appropriate Solaris patch to all systems.
Customer impacts if changes not applied:
  • Users will have incorrect time and/or date after TZ change occurs. There is no workaround for this issue. Patches/updates are required.
See also:


Directory Server, Directory Proxy Server, Directory Editor, Identity Synchronization from Windows




ECXpert (IS-B2B)

There is an impact to all versions of the software.
  • The OS is the only source of date/time information, the scheduler component stores target date/time to trigger future events.
  • All events in the system (transactional data, updates to configuration) are posted to the version of Oracle the customer is using; the application does not provide this date/time, but depends on Oracle to timestamp internally. The application requests this information for reporting through the UI. Events posted to the Oracle database always contain the date/time as provided to the stored procedure within Oracle.
  • Customers should contact Oracle directly for fixes specific to DST.
Products/versions affected:
  • ECXpert 3.6.3
    • Uses OS and Oracle (8 and 9i) to obtain DST
    • OS supported: Solaris 8, 9 (Sparc), Win NT 4, Win2000
    • Java versions supported: 1.4.2
  • ECXpert 3.6.2 (Currently in EOL)
    • Uses OS and Oracle (8 and 9i) to obtain DST
    • OS supported: Solaris 8 (Sparc), Win NT 4, Win2000
    • Java versions supported: 1.2.x
Customer actions needed: Customer impacts if changes not applied:
  • Customers using the scheduler component of ECXpert could possibly be affected for one-time and repeating events, if those events pass the commencement date for the new DST change. The scheduler receives the date and time from the operating system (never through Java) to compare against the stored schedule event.
  • Windows users, especially, if the operating system is not providing the correct adjustment, scheduled events will trigger off by 1 hour. If the operating system provides incorrect information, users of the scheduler would have to manually adjust their start times during the period of time covered by the extended DST.



Explorer and iRunbook

  • Not impacted.



File System Manager (FSM)

Products/version affected:
  • FSM 4.1, 4.2
    • Requires Java upgrades to avoid issues
    • OS supported: Solaris 8 Update 5 (Sparc), Solaris 9 (Sparc)
    • Java version supported: 1.4.1
  • FSM 4.3
    • Requires Java upgrades to avoid issues
    • OS supported: Solaris 8 Update 5 (Sparc), Solaris 9 (Sparc), Solaris 10 (Sparc)
    • Java versions supported: 1.4.2 (Solaris 8,9), 5.0 (Solaris 10)
  • FSM 4.4
    • Requires Java upgrades to avoid issues
    • OS supported: Solaris 9, 10 (Sparc), Solaris 10 (x86)
    • Java versions supported: 1.4.2 (Solaris 9), 5.0 (Solaris 10 Sparc/x86)
  • FSM 4.5
    • Requires Java upgrades to avoid issues
    • OS supported: Solaris 9, 10 (Sparc), Solaris 10 (x86)
    • Java versions supported: 1.4.2 (Solaris 9), 5.0 (Solaris 10 Sparc/x86)
  • FSM 4.6
    • Requires Java upgrades to avoid issues
    • OS supported: Solaris 9, 10 (Sparc), Solaris 10 (x86)
    • Java versions supported: 1.4.2 (Solaris 9), 5.0 (Solaris 10 Sparc/x86)
Customer actions needed: Customer impacts if changes not applied:
  • Displayed dates will be an 1 hour off in the affected date ranges.



HADB

Products/versions affected:
  • HADB 4.4.2.20 in Java ES 4/Application Server
    • OS supported: Solaris Sparc (8,9), Solaris x86 9, Redhat (Advanced Server 2.1, Enterprise Linux 3.0), Windows (2000, 2003)
  • HADB 4.4.3 in Java ES 5/Application Server
    • OS supported: Solaris Sparc (8,9,10), Solaris x86 (9,10), Redhat (Enterprise Linux 3.0, 4.0), Windows (2000, 2003)
  • HADB 4.5 in Storagetek 5800
    • OS supported: Solaris Sparc (8,9,10), Solaris x86 (9,10), Redhat (Enterprise Linux 3.0, 4.0), Windows (2000, 2003)
  • HADB 4.6 in Storagetek 5800
    • OS supported: Solaris Sparc (9,10), Solaris x86 (9,10), Redhat (Enterprise Linux 3.0, 4.0), Windows (2000, 2003)
Customer actions needed: Customer impacts if changes not applied:
  • Timestamp values entered into the database in the interim period between the new DST start date and the old will be off by one hour.



Identity Manager, Identity Auditor, Identity Manager SPE

All supported versions of Identity Manager (5.0, 5.5, 6.0, 7.0), Identity Auditor, and Identity Manager SPE and their service packs are affected unless the application server is running on a java version with the DST changes:
  • Java SE 6 or later
  • J2SE 5.0 Update 10 or later
  • J2SE 1.4.2_12 or later
  • J2SE 1.3.1_19 or later
Customer actions needed:
  • Gateway hosting time functions are obtained from Windows OS and must be updated: http://www.microsoft.com/windows/timezone/dst2007.mspx
  • Upgrade the java version in the application server to a compliant version. Follow the directions for your application server to complete the shutdown, upgrade, and restarting.
  • Review the list of tasks scheduled to start during time frame when daylight savings time changes will take effect. Items scheduled to start in this time frame prior to applying the DST patches will need to be rescheduled. Any recurring items which run at least once after the DST patch has been applied and before the new time change occurs will run at their expected times.
  • Refer to Java DST Information.
Customer impacts if changes not applied:
  • Some scheduled tasks (tasks, reconciliation, active sync) may run one hour off schedule depending on the specific scheduling parameters.
  • Reports may include or exclude events up to an hour outside the specified range.
  • Customer modifications with date dependencies may show erroneous results.



Java DB and Derby

Java DB is run on some combination of one OS and one Java version and will need to patch both the OS and Java for DST changes. Application of Java fixes requires a restart for changes to take effect.
  • Java DB 10.2.1, 10.2.2, 10.1.3, 10.1.1.0 in Appserver 8.2 and Derby 10.0.2.1 in Java ES 4.
  • Java DB 10.1.3 in Java ES 5 only will also be available on HP-UX 11v1, pa-risc. The Java version on HP-UX is HP version of Java 1.5.
  • Impacted OS'es and Java versions:
    • Solaris 8 (Sparc only), Solaris 9 and 10 (Sparc/x86)
    • Red Hat Enterprise Linux 3, 4
    • Windows 2000, 2003, XP
    • Java 1.4, 1.5 and 1.6 - link
Customer actions needed:


Java Desktop System (JDS)

  • JDS Solaris: Apply the Solaris DST patches. Refer to Sun Alert 234461.
  • JDS Linux: An update function is provided for JDS/Linux that allows the user to install patches.
    • Customer actions needed:
      • From the JDS Launch menu button, select:
        Launch ---> Applications ---> System Tools ---> Online Update
        You will be prompted for your password, enter the serial number of your host system and select the OS DST updates to install.



Java ES Installer

The Java ES installer bundles a J2SE runtime that is used as a bootstrap JRE to run the installer. The same version of J2SE is also carried by the installer and used to upgrade the host OS if the host OS has an older version of J2SE installed.

 

Products/versions affected:
  • Java ES 5: Not impacted.
    • Uses J2SE 1.5_09
    • OS supported: Solaris, Windows, Linux
  • Java ES 4 (2005Q4)
    • Uses J2SE 1.5.0_04
    • OS supported: Solaris 8 (SPARC), Solaris 9, 10 (SPARC/x86)
  • Java ES 3 (2005Q1)
    • Uses J2SE 1.5.0_01
    • OS supported: Solaris 8 (SPARC), Solaris 9, 10 (SPARC/x86)
  • Java ES 2 (2004Q2)
    • Uses J2SE 1.4.2_04
    • OS supported: Solaris 8 (SPARC), Solaris 9, 10 (SPARC/x86)
  • Java ES 1 (2003Q4)
    • Uses J2SE 1.4.1_06
    • OS supported: Solaris 8 (SPARC), Solaris 9, 10 (SPARC/x86)
For Java ES 1-4 the bundled version of J2SE contains vulnerabilities which can allow a remote, unauthenticated attacker to execute arbitrary code on a vulnerable system. Recommendation is to upgrade to:
  • JDK and JRE 5.0 Update 10 or later
  • SDK and JRE 1.4.2_13 or later
  • SDK and JRE 1.3.1_19 or later
Customer actions recommended: Customer impacts if changes not applied:
  • Log files may have timestamps that are off by one hour for installs performed during the new DST time periods.



Java ES Monitoring Framework (MF) and Monitoring Console (MC)

Products/versions affected:
  • Java ES MF/MC 1.0, 2.0
Customer actions needed:
  • Upgrade Java and apply OS patches. Restart Cacao (for Monitoring Framework) and Sun Web Console (for Monitoring Console).
    • To restart Cacao: /opt/SUNWcacao/bin/cacaoadm restart
    • To restart Sun Web Console: /usr/sbin/smcwebserver restart
Customer impacts if changes not applied:
  • Times reported by JES MF/JES MC may be off by one hour during some weeks.



Java ME

Java ME products are provided to commercial licensees only as source products and are not made available in binary form. These produ cts are not generally available and are supported directly by the Java ME team. For questions regarding these products contact DST-JLEsupport@sun.com.

 

Products/versions affected:
  • CDC: Fixes for the recent US DST update have been made available to Sun's source customers for releases of the CDC 1.0 and 1.1 configurations along with any associated profiles. For all future DST updates, source customers should contact their Java License Engineering representative for current release information.
  • CDC Toolkit: Version 1.0_01 contains the fix for the US DST update. Future DST updates are expected to be posted to the product webpage at here.
  • JDTS (Java Device Test Suite) 1.4 and earlier: Dependency on earlier versions of JDK which are affected. See below for specific actions needed for JDTS 1.4. JDTS 1.4 uses OS WinXP and Solaris 9, but does not require OS DST patches to be installed.
Products not affected:
  • CLDC/CLDC HI: Support only GMT.
  • JDTS 2.0
  • WTK 2.x : Binary versions of the Sun Java Wireless Toolkit available at http://www.oracle.com/technetwork/java are not impacted.
  • JavaCard: Version under development is affected but is not planned for release in the near future. Earlier versions are not impacted.
Customer actions needed for JDTS 1.4:
  • Stop JDTS 1.4 Admin/Console application
  • Upgrade JDK/JRE
  • Start applications again when necessary.
Customer impacts if changes are not applied:
  • Timestamps in the following reports may be incorrect if the JDK/JRE is not upgraded:
    • ImportProfile HTML report
    • JDTS 1.4 HTML Report
    • JDTS 1.4 XML Report (elements root/ReportInfo/GenerationTime and root/ReportInfo/MSGenerationTime)



JCAPS (includes former SeeBeyond)

Products/versions affected:
  • eWay Intelligent Adapters: All Versions (4.x, SRE 5.0.x, TRE 5.0.x, ICAN 5.0.x, CAPS 5.1.x)
    • Uses OS and JRE to obtain DST
    • OS supported: Solaris (2.6,8,9,10), Windows (2003, XP, 2000), AIX (5.3, 5.2), HP/UX (11i v2.0 (11.23) on Itanium, 11i (11.11) on PA-RISC, 11.0 on PA-RISC), Tru64 (5.1B, 5.1A), Red Hat (Advanced Server 3.0, 2.1), Suse Linux (Enterprise Server 8, 9)
    • JRE Versions:
      • 4.x: JRE 1.3.x
      • SRE 5.0.x/TRE 5.0.x: JRE 1.3.x
      • ICAN 5.0.x: JRE 1.4.x
      • CAPS 5.1.x: JRE 1.4.x and JRE 1.5.x
  • eVision Studio: All Versions (ICAN 5.0.x ad CAPS 5.1.x)
    • Uses OS and JRE to obtain DST
    • OS supported: Solaris (8,9,10), Windows (2003, XP, 2000), AIX (5.3, 5.2), HP/UX (11i v2.0 (11.23) on Itanium, 11i (11.11) on PA-RISC, 11.0 on PA-RISC), Tru64 (5.1B, 5.1A), Red Hat (Advanced Server 3.0, 2.1), Suse Linux (Enterprise Server 8, 9)
    • JRE Versions:
      • ICAN 5.0.x: JRE 1.4.x
      • CAPS 5.1.x: JRE 1.4.x and JRE 1.5.x
  • OTD (ETD) Libraries: All Versions (4.x, SRE 5.0.x, TRE 5.0.x, ICAN 5.0.x, CAPS 5.1.x)
    • Uses OS and JRE to obtain DST
    • OS supported: Solaris (2.6,8,9,10), Windows (2003, XP, 2000), AIX (5.3, 5.2), HP/UX (11i v2.0 (11.23) on Itanium, 11i (11.11) on PA-RISC, 11.0 on PA-RISC), Tru64 (5.1B, 5.1A), Red Hat (Advanced Server 3.0, 2.1), Suse Linux (Enterprise Server 8, 9)
    • JRE Versions:
      • 4.x: JRE 1.3.x
      • SRE 5.0.x/TRE 5.0.x: JRE 1.3.x
      • ICAN 5.0.x: JRE 1.4.x
      • CAPS 5.1.x: JRE 1.4.x and JRE 1.5.x
  • eTL Integrator: All Versions (ICAN 5.0.x, CAPS 5.1.x)
    • Uses OS and JRE to obtain DST
    • OS supported: Solaris (8,9,10), Windows (2003, XP, 2000), AIX (5.3, 5.2), HP/UX (11i v2.0 (11.23) on Itanium, 11i (11.11) on PA-RISC, 11.0 on PA-RISC), Tru64 (5.1B, 5.1A), Red Hat (Advanced Server 3.0, 2.1), Suse Linux (Enterprise Server 8, 9)
    • JRE Versions:
      • ICAN 5.0.x: JRE 1.4.x
      • CAPS 5.1.x: JRE 1.4.x and JRE 1.5.x
  • eXpressway Integrator: All Versions (4.x, SRE 5.0.x)
    • Uses OS and JRE to obtain DST
    • OS supported: Solaris (2.6,8,9,10), Windows (2003, XP, 2000)
    • JRE Versions:
      • 4.x: JRE 1.3.x
  • eXchange Integrator: All Versions (4.x, SRE 5.0.x, TRE 5.0.x, ICAN 5.0.x, CAPS 5.1.x)
    • Uses OS and JRE to obtain DST
    • OS supported: Solaris (8,9,10), Windows (2003, XP, 2000), AIX (5.3, 5.2), HP/UX (11i v2.0 (11.23) on Itanium, 11i (11.11) on PA-RISC, 11.0 on PA-RISC), Tru64 (5.1B, 5.1A), Red Hat (Advanced Server 3.0, 2.1), Suse Linux (Enterprise Server 8, 9)
    • JRE Versions:
      • 4.x: JRE 1.3.x
      • SRE 5.0.x/TRE 5.0.x: JRE 1.3.x
      • ICAN 5.0.x: JRE 1.4.x
      • CAPS 5.1.x: JRE 1.4.x and JRE 1.5.x
  • eBAM Studio: All Versions (ICAN 5.0.x ad CAPS 5.1.x)
    • Uses OS and JRE to obtain DST
    • OS supported: Solaris (8,9,10), Windows (2003, XP, 2000), AIX (5.3, 5.2), HP/UX (11i v2.0 (11.23) on Itanium, 11i (11.11) on PA-RISC, 11.0 on PA-RISC), Tru64 (5.1B, 5.1A), Red Hat (Advanced Server 3.0, 2.1), Suse Linux (Enterprise Server 8, 9)
    • JRE Versions:
      • ICAN 5.0.x: JRE 1.4.x
      • CAPS 5.1.x: JRE 1.4.x and JRE 1.5.x
  • eInsight Business Process Manager: All Versions (4.x, SRE 5.0.x, TRE 5.0.x, ICAN 5.0.x, CAPS 5.1.x)
    • Uses OS and JRE to obtain DST
    • OS supported: Solaris (2.6,8,9,10), Windows (2003, XP, 2000), AIX (5.3, 5.2), HP/UX (11i v2.0 (11.23) on Itanium, 11i (11.11) on PA-RISC, 11.0 on PA-RISC), Tru64 (5.1B, 5.1A), Red Hat (Advanced Server 3.0, 2.1), Suse Linux (Enterprise Server 8, 9)
    • JRE Versions:
      • 4.x: JRE 1.3.x
      • SRE 5.0.x/TRE 5.0.x: JRE 1.3.x
      • ICAN 5.0.x: JRE 1.4.x
      • CAPS 5.1.x: JRE 1.4.x and JRE 1.5.x
  • eGate Integrator: All Versions (4.x, SRE 5.0.x, TRE 5.0.x, ICAN 5.0.x, CAPS 5.1.x)
    • Uses OS and JRE to obtain DST
    • OS supported: Solaris (2.6,8,9,10), Windows (2003, XP, 2000), AIX (5.3, 5.2), HP/UX (11i v2.0 (11.23) on Itanium, 11i (11.11) on PA-RISC, 11.0 on PA-RISC), Tru64 (5.1B, 5.1A), Red Hat (Advanced Server 3.0, 2.1), Suse Linux (Enterprise Server 8, 9)
    • JRE Versions:
      • 4.x: JRE 1.3.x
      • SRE 5.0.x/TRE 5.0.x: JRE 1.3.x
      • ICAN 5.0.x: JRE 1.4.x
      • CAPS 5.1.x: JRE 1.4.x and JRE 1.5.x
  • eView Studio: All Versions (ICAN 5.0.x, CAPS 5.1.x)
    • Uses OS and JRE to obtain DST
    • OS supported: Solaris (8,9,10), Windows (2003, XP, 2000), AIX (5.3, 5.2), HP/UX (11i v2.0 (11.23) on Itanium, 11i (11.11) on PA-RISC, 11.0 on PA-RISC), Tru64 (5.1B, 5.1A), Red Hat (Advanced Server 3.0, 2.1), Suse Linux (Enterprise Server 8, 9)
    • JRE Versions:
      • ICAN 5.0.x: JRE 1.4.x
      • CAPS 5.1.x: JRE 1.4.x and JRE 1.5.x
  • Protocol Managers: All Versions (ICAN 5.0.x, CAPS 5.1.x)
    • Uses OS and JRE to obtain DST
    • OS supported: Solaris (8,9,10), Windows (2003, XP, 2000), AIX (5.3, 5.2), HP/UX (11i v2.0 (11.23) on Itanium, 11i (11.11) on PA-RISC, 11.0 on PA-RISC), Tru64 (5.1B, 5.1A), Red Hat (Advanced Server 3.0, 2.1), Suse Linux (Enterprise Server 8, 9)
    • JRE Versions:
      • ICAN 5.0.x: JRE 1.4.x
      • CAPS 5.1.x: JRE 1.4.x and JRE 1.5.x
Customer actions needed:


JWS Developer Pack (JWSDP)

Products/versions affected:
  • JWSDP 2.0, 2.1
    • Uses JDK to obtain DST, JDKs supported: 1.5 or above
    • OS supported: Solaris 9 (Sparc, x86), Solaris 10 (Sparc, x64), Windows 2003 Server Professional Edition, Windows XP Professional Edition, Windows 2000 Professional Edition, RedHat Linux 9.0, RedHat Linux AS 3.0 (including Update 4)
  • JWSDP 1.6
    • Uses JDK to obtain DST, JDKs supported: 1.4.2, 1.5
    • OS supported: Solaris 9, 10 (Sparc, x86), Windows 2003 Server Professional Edition, Windows XP Professional Edition, Windows 2000 Professional Edition, RedHat Linux 9.0, RedHat Linux AS 3.0
  • JWSDP 1.5, 1.5.1
    • Uses JDK to obtain DST, JDKs supported: 1.4.2, 1.5
    • OS supported: Solaris 9 (Sparc, x86), Windows 2003 Server Professional Edition, Windows XP Professional Edition, RedHat Linux 9.0
  • JWSDP 1.4
    • Uses JDK to obtain DST, JDKs supported: 1.4.2
    • OS supported: Solaris 9 (Sparc, x86), Windows 2003 Server Professional Edition, Windows XP Professional Edition, RedHat Linux 9.0
  • JWSDP 1.3
    • Uses JDK to obtain DST, JDKs supported: 1.4.2
    • OS supported: Solaris 8 (Sparc), Solaris 9 (Sparc, x86), Windows 2000 Professional Edition, Windows XP Professional Edition, RedHat Linux 8.0
Customer actions needed:
  • Upgrade the JDK/JRE used by JWSDP to support the new Date/Time information.
  • Restart container.
Customer impacts if changes not applied:
  • Times reported by JWSDP technologies may be off by one hour during some weeks.

 

NOTE: Above applies to JAX* technologies from JWSDP used by Sun Java System containers. Steps taken for these containers should address the needed fixes.


Calendar Server

  • Calendar Server 5.1.1, 6.0, 6.1 and 6.2
    • Uses application specific file (timezones.ics) for DST
    • OS supported: Solaris Sparc/x86 (8,9,10), Windows (2000 Advanced Server, SP4, 2003 Enterprise Server, XP SP1 and SP2), HP-UX 11i, Red Hat Linux (2.1,3.0)
    • Note: Date/Time is converted and stored in GMT. There is no way to determine GMT offset used for the conversion, after an event has been created.
      After updating the timezone information file, pre-existing events scheduled for the days between the old and new change-over dates will show a one hour discrepancy. To address these problem events, customers can edit the single events and the instances of recurring series that fall in the above time period to reflect the correct time. In the case of events with attendees, the organizer can edit the events and that change will be reflected in an attendee's calendar.



Messaging Server, Communications Express, Delegated Admin, Comms Sync, Outlook Connector, Instant Messaging

Products/versions affected:
  • Delegated Admin: Not impacted.
  • Comms Sync: Not impacted.
  • Communications Express 6.1, 6.2
    • Uses JDK for obtain DST
    • JDKs supported: JDK 1.3, 1.4 and 1.5
    • OS supported: Solaris Sparc/x86 (9,10), Red Hat Linux 2.1
  • Instant Messaging Server 7.2
    • Uses JDK for obtain DST
    • JDKs supported: JDK 1.5.0
    • OS supported: Solaris Sparc/x86 (8,9,10), Red Hat Linux (2.1,3.0)
  • Messaging Server 5.2, 6.0, 6.1, 6.2
    • Uses OS to obtain DST
    • OS supported: Solaris Sparc/x86 (2.6,8,9,10), Red Hat Linux (2.1,3.0), Windows (2000 Advanced Server, SP4, 2003 Enterprise Server, XP SP1 and SP2), HP-UX 11i
  • Outlook Connector 7.1, 7.2
Application restart required for all products. Customer actions needed:
  • Install all necessary OS patches to address the DST issue in the OS (Messaging)
  • Refer to Java DST Information.
  • Restart the server
Customer impacts if changes not applied:
  • Communications Express: Application may report incorrect time.
  • Instant Messaging: Message and log timestamps will be inaccurate.
  • Messaging Server: Incorrect date/time in email messages.



Message Queue

Message Queue does not ship with the JDK, however, application time/date information is obtained by the Java version resident on the Customer system. The JDK (Java) versions below indicate the supported Java versions that will need to be updated for Message Queue to provide correct timestamp data after DST changes go into effect.

 

Products/versions affected:
  • Message Queue 3.0.1, 3.0.1SP1, 3.0.1SP2, 3.0.1SP3
    • Uses JDK to obtain DST
    • Supported JDK 1.4
    • OS supported: Solaris Sparc (8,9 10), Windows (XP Pro, 2000 Pro SP2, 2000 Server SP2, Advanced Server SP2), Redhat Linux 7.1
  • Message Queue 3.5, 3.5SP1, 3.5SP2
    • Uses JDK to obtain DST
    • Supported JDK 1.4.2_02
    • OS supported: Solaris Sparc (8,9,10), Solaris x86 (9,10), Windows (XP Pro, XP3, 2000 Pro SP3, .NET Server 2003 Enterprise Edition, 2000 Advanced Server SP3), Redhat Linux Advanced Server 2.1 Update 2
  • Message Queue 3.6, 3.6SP1, 3.6SP2, 3.6SP3, 3.6SP4
    • Uses JDK to obtain DST
    • Supported JDK 4.2_06, 1.5
    • OS supported: Solaris 8 Update 7 (sparc), Solaris 9 update 8 (sparc/x86), Solaris 10 (sparc/x86), Windows (XP Pro SP4, Advanced Server SP4, 20003 Server SP4), Redhat Linux (Advanced Server: 2.1 Update 2, 3.0 Update 1), HP-UX 11.11 (PA-RISC)
  • Message Queue 3.7, 3.7UR1
    • Uses JDK to obtain DST
    • Supported JDK 6.0, 1.5.0_08, JDK 1.4.2_10
    • OS supported: Solaris 9 Update 7 (sparc,x86), Solaris 10 Update 2 (sparc,x86,x64), Redhat Linux (3.0 Update 6, 4.0 for x64), Windows (2000 Server SP4, 2003 Server SP1, XP Pro SP2), HP-UX 11.11 (PA-RISC)
  • Message Queue 4.0
    • Uses JDK to obtain DST
    • Supported JDK 1.5.0_06, 1.4.2_06
    • OS supported: Solaris 9 Update 7 (Sparc,x86), Solaris 10 Update 2 (sparc,x86,x64), Redhat Linux (3.0 Update 6, 4.0 for x64), Windows (2000 Server SP4, 2003 Server SP1, XP Pro SP2)
Customer actions needed:
  • Upgrade the JDK/JRE used by MQ to support the new Date/Time information
  • Restart the MQ server (the broker)
Customer impacts if changes not applied:
  • Timestamps in the Log files may be incorrect.



Mozilla

No specific Mozilla patches are required for DST compliance.

To determine the version of Java used by Mozilla, bring up the Help->About Plug-ins menu item from Mozilla. The Java version used by Mozilla will be displayed.

Products/versions affected:
  • Mozilla 1.7 bundled with Solaris 10
    • Uses Java version bundled with Solaris 10 to run Java applets and, Solaris OS for JavaScript applications to obtain DST information.
  • Mozilla 1.7 unbundled for Solaris 8 and 9 (Sparc/X86)
    • Uses an unbundled Java version 1.5.0_05 or the Java version bundled with Solaris 8 and 9 to run Java applets. Uses the Solaris OS for JavaScript applications to obtain DST information.
  • Mozilla 1.4: EOL
    • Uses unbundled Java 1.4.2_02 or the Java version bundled with Solaris 8 and 9 to run Java applets. Uses the Solaris OS for JavaScript applications to obtain DST information.
Customer actions needed: Customer impacts if changes not applied:
  • Times reported in JavaScript applications or Java applets may be off by one hour during some weeks.



N1 Grid Engine

Products/versions affected:
  • N1 Grid Engine 5.3
    • Uses OS to obtain DST
    • OS supported: Solaris 2.6, 7, 8, 9, 10
  • N1 Grid Engine 6.0
    • Uses Java and OS to obtain DST
    • Java version 1.4
      • J2SE 1.4.2_13 or J2SE 5.0 Update 10 or later is needed
    • OS supported: Solaris 7, 8, 9, 10
Customer actions needed:


N1 Service Provisioning System (N1 SPS)

Products/versions affected:
  • N1 SPS 5.0, 5.1, 5.2, 5.2 U1, 5.2 U2
    • Uses JDK to obtain DST
    • JDK supported: 1.4.2
    • OS supported: Solaris Sparc (10,9,8,7), Solaris x86 (10,9), Windows Server 2003 (Web, Enterprise, Standard and Datacenter Editions), Red Hat Linux Advanced Server (4.0, 3.0, 2.1), HP-UX 11i, SuSE Linux Enterprise (9,8)
Customer actions needed: Customer impacts if changes not applied:
  • Scheduling in application will be impacted.
  • N1SPS UI and the log files will have incorrect timestamp.



N1 System Manager (N1 SM)

Products/versions affected:
  • N1 SM 1.2,1.3, 1.3.1, 1.3.2
    • Uses JDK to obtain DST
    • JDK supported: 1.4.2, 1.5.0
    • OS supported: Solaris x64 (9,10), Solaris 10 Sparc, Red Hat Enterprise Linux AS/ES/WS (3.0 update 2 or later, 4.0 or later), SuSE Linux Enterprise Server 9.0, SuSE Professional Linux 9.3, 9.2, Windows (2003SE/2003EE, 2003WE, 2000S/2000AS)
Customer actions needed:
  • Apply patch for JDKs on the management server.
    • Refer to Java DST Information.
    • Shutdown the N1SM management server before applying the JDK patch. Update all the JDK instances started by N1SM
  • Apply OS patches on the management server and the managed servers.
Customer impacts if changes not applied:
  • Scheduling in application will be impacted.
  • OS monitoring may be impacted.
  • N1SM UI and the log files will have incorrect timestamp.



Net Connect

Products/versions affected:
  • NetConnect Client Bundle(ncproviders + proxy) 3.1.1, 3.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4
    • Uses Java and Sun OS to obtain DST
    • Java supported: 1.4.2 or higher
    • OS supported: Solaris Sparc (10,9,8)
  • NetConnect DMM 3.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4
    • Uses Java and Sun OS to obtain DST
    • Java supported: 1.4.2.x (Java 5.0 and 6.0 are not supported)
    • OS supported: Solaris Sparc (10,9,8)
Customer actions needed: Customer impacts if changes not applied:
  • Incorrect timestamp for generated events.
  • Incorrect timestamp in log messages.
  • Scheduling in application will be impacted.



Portal Server

Customer impacts if changes not applied:


PostgreSQL

PostgreSQL is part of Solaris 10 and has its own timezones information stored in the /usr/share/pgsql/timezone/ directory. This section only applies to PostgreSQL within Solaris 10. Other products which include postgres: N1 Service Provisioning System (N1 SPS) and N1 System Manager (N1 SM) running on non-Solaris platforms will need to install the applicable OS DST fixes.

 

NOTE: Customers using the postgres JDBC driver for Solaris will need to upgrade Java. Refer to Java DST Information for updates and tzupdater tool.

 

Products/versions affected: Products not affected:
  • PostgreSQL 8.2
  • PostgreSQL 8.1.6, released on Monday 8th January.
Customer actions needed:
  • Download applicable PostgresSQL patch
  • Stop PostgresSQL server
  • Apply patch
  • Start PostgresSQL server
Customer impacts if changes not applied:
  • Date/time arithmetic and conversion will generate the wrong result for date in the affected date range.
Also see http://www.postgresql.org/docs/faqs.FAQ.html#item1.14 for additional information.


SAM-QFS

  • Not impacted.
  • Caveat: SAM-QFS uses libc (Unix time), which is not affected by DST. Where Customers have converted from Unix to local time, Solaris OS patches need to be applied to avoid DST issues with certain Solaris commands which would display the time incorrectly during the affected date ranges.



Secure Global Desktop (SGD)

  • See InfoDoc 88256 - Understanding impact of US Daylight Savings Time Changes with Sun[TM] Secure Global Desktop
  • The customer may need to update their OS or any Java versions used by other applications but this is independent of the SGD server and clients.



Service Registry

Current Customer base is running J2SE 5.0 update 9 which has 2007 U.S., Western Australia, Bahamas and other DST changes. Refer to Java DST Information.

 

Products/versions affected:
  • Service Registry: 3.0 (Java ES 4)
  • Service Registry: 3.1 (Java ES 5)



Shared Shell Client

Products/versions affected:
  • Shared Shell V 4.0
    • Uses Java to obtain DST
    • Java supported: 1.4.2 and later
    • OS supported: Solaris, Windows, Linux
The Shared Shell client is supported on all OS and processor architectures that the Sun JVM, version 1.4.2 and up, is supported on. Refer to: Customer actions needed: Customer impacts if changes not applied:
  • Log files on initiator system would show incorrect timestamps in affected date range.



Simple Network Management Protocol (SNMP)

  • Not affected.



Solaris Cluster (Sun Cluster)

Products/versions affected:
  • Sun Cluster 2.2
    • OS supported: Solaris 2.6, 7, 8 (Sparc)
  • Sun Cluster 3.0
    • OS supported: Solaris 8, 9 (Sparc)
  • Sun Cluster 3.1
    • OS supported: Solaris 8 (Sparc), Solaris 9 (Sparc, x86), Solaris 10 (Sparc, x86, x64)
  • Sun Cluster 3.2
    • OS supported: Solaris 9 (Sparc, x86), Solaris 10 (Sparc, x86, x64)
Customer actions needed:
NOTE: Sun Cluster does not ship with Java, but uses whatever version is installed on the system. Customers will need to update Java as applicable to the deployment. Customer impacts if changes not applied:
  • The timestamps in the log files will be inaccurate across the cluster nodes if OS patches are not installed.
    • As an example, if the Solaris patch is applied at time T1 on node1 and at time T2 on node2, then comparing messages between T2 and T1 will have to take into account the time change when correlating the messages between the nodes.



Solaris Management Console (SMC)

Products/versions affected
  • SMC 2.0, 2.1
    • Uses Solaris and JDK to get DST info
    • OS supported: Solaris 8,9,10 (Sparc, x86)
    • Java versions supported:
      • 1.2.2_06 (Solaris 8) - upgrade to 1.3.1_19 or later
      • J2SE 1.4.2_11 or later (Solaris 9) - upgrade to 1.4.2_13
      • J2SE 5.0 Update 6 or later (Solaris 10) - upgrade to 5.0 Update 10
Customer actions needed: Customer impacts if changes not applied:
  • Scheduling in SMC will be broken. System Information, Log Viewer and Logs will have incorrect timestamps in affected date ranges.



Staroffice/Starsuite

Product/versions affected:
  • Staroffice/Starsuite 6:
    • Solaris 7 (SPARC/x86) or higher
    • Windows 95, 98, ME, NT, 2000 or XP
    • Linux Kernel version 2.2.13 or higher, glibc2 version 2.1.3 or higher
  • Staroffice/Starsuite 7:
    • Solaris 8 (Sparc only) or higher
    • Windows 98, ME, NT (Service Pack 6 or higher), 2000 (Service Pack 2 or higher) or XP
    • Linux Kernel version 2.2.13 or higher, glibc2 version 2.2.0 or higher
  • Staroffice/Starsuite 8:
    • Solaris 8 (Sparc/x86) or higher
    • Windows 98, ME, 2000 (at least Service Pack 2) or XP
    • Linux Kernel version 2.4 or higher, glibc2 version 2.3.2 or higher
Customer actions needed:
  • OS level patches will need to be applied for DST changes for Staroffice 6, 7 and 8.



StorADE

StorADE gets its time information from the system clock only.

 

Products/versions affected:
  • StorADE 2.2
    • Uses OS to obtain DST
    • OS supported: Solaris 8 (Sparc)
  • StorADE 2.3
    • Uses OS to obtain DST
    • OS supported: Solaris 8, 9 (Sparc)
  • StorADE 2.4
    • Uses OS to obtain DST
    • OS supported: Solaris 9, 10 (Sparc)
Customer actions needed:
  • Install applicable OS patches, see Sun Alert 234461 for Solaris OS specific patches.
Customer impacts if changes are not applied:
  • Timing information displayed will be off by 1 hour in affected date range.



Sun Management Center (Sun MC)

Products/versions affected:
  • Sun MC 3.5, 3.6, 3.6.1
    • Uses JDK to obtain DST
    • JDK supported: 1.4.2 or higher
    • OS supported: Solaris 7 to 10 OS, Linux kernel 2.4, 2.6
Products not affected:
  • Sun Management Center 3.6 platform addons (e.g. SunFire 10000K, Serengeti, Entry-Level Products, Workstation, etc.)
Customer actions needed:
  • Apply patches for OS and JDK.
  • Application restart is required after applying the JDK patch.
Customer impacts if changes not applied:
  • Alarms are displayed inside SunMC console. The data is collected using GMT and on the console data is displayed in the console's time zone. If Java patch is not applied the DST data may appear incorrectly with the patch it displays correctly.



Sun Preventive Services - Availability Appliance (SPS-AA)

Products/versions affected:
  • SPS-AA 2.0, 2.0.1, 2.0.2, 2.1
    • Uses Java and Sun OS to obtain DST
    • Java supported: Bundled - 1.4.2_11, 1.5.0_06b05
    • OS supported: Solaris 9, 10 (Sparc, x86)
Customer actions needed: Customer impacts if changes not applied:
  • No major impact other than cron jobs would run off by an hour.
  • All reports and log files will show incorrect time stamp n affected date range.



Sun Ray Software

Products/versions affected:
  • Sun Ray Server Software 3.0
    • OS supported: Solaris 8 2/02 (Sparc), Solaris 9 12/03 (Sparc), Trusted Solaris 8 7/03 (Sparc), Sun JDS 2, SuSE SLES 8.0 SP3, RHEL AS 3
  • Sun Ray Server Software 3.1
    • OS supported: Solaris 8 Update 7 (Sparc), Solaris 9 Update 7 (Sparc), Solaris 10 (Sparc), Trusted Solaris 8 7/03 (sparc), Trusted Solaris 8 2/04 (Sparc), Solaris 10 (x86)
  • Sun Ray Server Software 3.1.1
    • OS supported: SLES 9 Service Pack 3 (x86), RHEL AS 4 Update 3 (x86)
  • Sun Ray Connector for Windows 1.1
    • OS supported: Solaris 8 Update 7 (Sparc), Solaris 9 Update 7 (Sparc), Solaris 10 (Sparc), Trusted Solaris 8 7/03 (Sparc), Trusted Solaris 8 2/04 (Sparc), Solaris 10 (x86), SLES 9 Service Pack 3 (x86), RHEL AS 4 Update 3 (x86)
  • Sun Desktop Manager 1.0
    • OS supported: Solaris 10 (Sparc, x86)
  • Sun Ray Connector 1.0
    • OS supported: Solaris 8 Update 7 (Sparc), Solaris 9 Update 7 (Sparc), Solaris 10 (Sparc), Trusted Solaris 8 7/03 (sparc), Trusted Solaris 8 2/04 (Sparc), Solaris 10 (x86)
Customer actions needed: Customer impacts if changes are not applied:
  • Debug output to log files will be off by 1 hour in the affected date range.



Sun Resource Manager (SRM) also known as Solaris Resource Manager

Sun Resource Manager is bundled in Solaris and requires the application of the Solaris OS patches.


Sun StorEdge Remote Response (SSRR)

Products/versions affected:
  • SSRR 1.1.3.8
    • Uses OS to obtain DST
    • OS supported: Solaris 8, 9, 10 (Sparc)
Customer actions needed:
  • Call Sun field engineer / Account representative for remedy.
    • NOTE: No access to SSRR OS is provided to customers. Individual patches are not supported on the images. The OS is delivered as part of a bundle of OS and applications. Patching the JRE may cause the management applications on the older OS images to lose data.
Customer impacts if changes not applied:
  • Events and logs would show incorrect time in affected date range.



Unified Development Server (UDS) and Integration Server, Enterprise Application Integration (IS EAI)

NOTE: Integration Server, Enterprise Application Integration is a workflow product built entirely using UDS and inherits all the characteristics of UDS.

 

Products/versions affected:
  • UDS 5.x and IS EAI 3.x (earlier dot releases are no longer supported)
    • Uses OS to obtain DST
    • OS supported: Solaris 8-10 (Sparc), HP/UX 11, AIX 5.1 and 5.2, Windows 2000/2003/XP
    • Java versions supported: 1.3 and later (Java not required for this product)
Customer actions needed: Customer impacts if changes not applied:
  • Applications created using these products may return incorrect results if the appropriate OS patches are not applied.



Update Connection Enterprise/System, SCRK, Basic Registration

Products/versions affected:
  • Sun Update Connection Enterprise 1.0, 1.1 (will release on February 15, 2007)
    • Obtains timezone information from the OS.
    • OS supported: Solaris 10 (Sparc, x86, x64), Red Hat RHEL 4 AS/ES, Novell SuSE SLES 9
  • Sun Update Connection System - Sun Connection Update Manager 1.0.4, 1.0.8, 1.0.9 (will release in February 2007)
    • Obtains timezone information from the OS.
    • OS supported: Solaris 10 (Sparc, x86)
  • SCRK 1.1. 1.1.1, 1.2, 1.3 (to be released in Q3)
    • Obtains timezone information from the OS.
    • OS supported: Solaris 8, 9 and 10 (SPARC, x86)
  • Basic Registration 1.1.1
    • Obtains timezone information from the OS.
    • OS supported: Solaris 10 (Sparc, x86)
Application restart required for all products.

Customer actions needed:

  • Install all necessary OS patches to address the DST issue in the appropriate OS
Customer impacts if changes not applied:
  • Sun Update Connection Enterprise: If OS patch to address DST is not available the Sun UCE KGM (Knowledge Generation Machine) will not update the customers SDS (Dependency Server) with the DST patch. UCE will not deliver the DST patch as a part of the patch bundle for the appropriate OS.
  • Sun Update Connection System: If the OS patch to address DST is not available the product (Sun Update Connection System) will not be able to deliver the update.



Web Server, Proxy Server, Active Server Pages Server (Webtier), Reverse Proxy plugin (RPP), Fast CGI (Common Gateway Interface)

Products/versions affected:
  • Active Server Pages (ASP) Server 4.0.x
    • Uses OS to obtain DST, uses JRE 1.4.2_06
    • Requires OS patches and Java upgrades to be installed
    • OS supported: Solaris SPARC (8,9,10), Solaris x86 (9, 10), Windows (XP, 2000 Server, 2003 Server), Red Hat Linux (2.1), HP-UX (11i), AIX (5.1, 5.2)
  • Web Server 7.0: DST Compliant
    • Uses JDK to obtain DST, JDKs supported: 1.5.0_09, 6.0
    • Requires OS patches and Java upgrades to be installed
    • OS supported: Solaris SPARC (8,9,10), Solaris x86 (10), Solaris AMD64 (10), Windows (XP, 2003 Server), Red Hat Linux (3.0, 4.0), SUSE (Enterprise Server 9), HP-UX (11i)
  • Web Server 6.1
    • Uses JDK and OS to obtain DST
    • JDK supported
      • 6.1 (default is 1.4.2_04), update to 1.4.2_13 or higher. Alternatively, use the tzupdater tool
      • 6.1SP1 through SP6 (default is 1.4.x), update to 1.4.2_13 or higher. Alternatively, use the tzupdater tool
      • WS6.1SP7 will use 1.4.2_13
      • On-going actions: Bundling New JDK (1.4.2_13) for Solaris, Linux, Windows having DST fixes. Product will be certified with DST fixes.
      • HPUX and AIX: JDK will not be included after SP7. Product will be certified with DST fixes.
    • Requires OS patches to be installed
    • OS supported: Solaris SPARC (8,9,10), Solaris x86 (9,10), Windows (XP, 2000 Server, 2003 Server), Red Hat Linux (2.1, 3.0, 4.0), HP-UX (11i), AIX (5.1, 5.2, 5.3)
  • Web Server 6.0: EOL Limited Support (Product has crossed last bug fix date May 14th, 2006.)
    • Uses JRE and OS to obtain DST
    • Recommendation is to update to 1.3.1_19, 1.4.2_13 or higher (default is 1.2.x).
      • Note: If already using Java 1.4.x or higher, you can use the tzupdater tool as an alternative to applying updates. The preferred recommendation is to apply the updates.
    • Requires OS patches and Java upgrades to be installed
    • OS supported: Solaris SPARC (2.6,7,8,9), Solaris x86 (9,10), Windows (2000 Server, NT), Red Hat Linux (7.2, 2.1), HP-UX (11.0, 11i), AIX (4.3.3, 5.1)
  • Web Server 4.1: EOSL
  • Web Proxy Server 4.0.x
    • Uses JRE and OS to obtain DST
    • JRE supported: 1.4.2_4
      • WPS4.0.4 will have the DST changes and distributed in Java ES 5 (Java ES 5 is DST compliant).
      • Versions prior to 4.0.4 will need to update Java to 1.4.2_13 or use the tzupdater tool.
    • Requires OS patches and Java upgrades to be installed
    • OS supported: Solaris SPARC (9,10), Solaris x86 (9,10), Windows (XP, 2000 Server, 2000 Advanced Server, 2003 Server), Red Hat Linux (2.1, 3.0, 4.0)
  • Web Proxy Server 3.6
    • Uses OS to obtain DST
    • Requires OS patches to be installed.
    • OS supported: Solaris SPARC, Windows, HP-UX, AIX
  • Reverse Proxy plugin (RPP)
    • Dependency on Web Server. DST works in plugin if Web Server handles DST correctly.
  • Fast CGI (Common Gateway Interface)
    • Dependency on Web Server. DST works in plugin if Web Server handles DST correctly.
Application restart required for all products except Reverse Proxy plugin (RPP) and Fast CGI (Common Gateway Interface).
Note: Java mitigations need to be applied when the application stack above the JRE are shutdown.

Customer actions needed:

  • Shutdown server(s) by using Admin console
  • Install all necessary OS patches to address the DST issue in the OS
  • If using Java, Refer to Java DST Information.

Customer impacts if changes not applied:

  • Web Server: Log entries will have incorrect timestamp; log rotation will not occur in correct date/time. Web applications using system time information will have incorrect timestamps in affected date ranges.
  • Web Proxy Server: Log entries will have incorrect timestamp; log rotation will not occur in correct date/time.
  • Active Server Pages (ASP): Application may report incorrect date/time. Log files may contain incorrect date/time.




Change Log

Note: This Change Log only reflects changes made to this web page. Please refer to product specific information for details of product updates.
  • [2008-09-09] Removed two outdated bullet points from Solaris section.
  • [2008-06-13] Updated references to Sun Alert 103044 to refer to the new SunAlert 234461.
  • [2007-10-25] Removed temporary Calendar Server link to obsolete files and documentation.
  • [2007-10-24] Updated Java section to link to Java home site.
  • [2007-10-11] Added link to Timezones, Daylight Savings, and the Sun TZupdater for the Java Runtime Environment (JRE) pages.
  • [2007-09-20] Added link to Calendar Server Sun Alert for NZ/Mongolia.
  • [2007-08-22] Updated US specific links for Solaris to refer to DST Sun Alert 103044.
  • [2007-08-22] Updated US specific links for Java to refer to main Java DST main information page.
  • [2007-08-22] Updated content for Java ME to include current changes.
  • [2007-08-22] Corrected text for Java impacts.
  • [2007-08-22] Added New Zealand (NZ) DST information for Solaris, Java.
  • [2007-08-22] Separated Calendar Server from grouping since product specific patches are required, added Calendar Server New Zealand patch information.
  • [2007-03-21] Added content for Mozilla.
  • [2007-03-12] Added additional information for customer actions needed.
  • [2007-03-09] Added link to Sun Alert for systems managed by Desktop Management Interface (DMI).
  • [2007-03-08] Added Sun Alert link 102836 for Java Olson Timezone (TZ) data, version 2005r or greater, may break backward compatibility for the Eastern, Hawaiian, and Mountain time zones.
  • [2007-03-08] Updated steps for Calendar Server DST Fix Tool.
  • [2007-03-08] Added CST Server/Agent steps for applying patches/updates.
  • [2007-03-07] Added links to Calendar Server DST Fix Tool
  • [2007-03-01] Added note/DST patch IDs for PostgreSQL 8.1.x
  • [2007-02-27] Updated Customer actions needed and impacts statements.
  • [2007-02-27] Added note for Java v1.3.1_20 for non-contract customers using Java SE v1.3.x
  • [2007-02-26] Added information for the 1.3.1 version of the tzupdater tool.
  • [2007-02-20] Removed reference to TS 8 HW 4/01 x86 patches (not provided with this version).
  • [2007-02-20] Added comment to clarify customer actions needed for event rescheduling.
  • [2007-02-20] Added note in CDE section to restart the rpc.cmsd daemon after applying OS patches.
  • [2007-02-16] Added link to Solaris Vintage page (same process/pricing).
  • [2007-02-15] Removed reference to pending Sun Alert as there are no Oracle specific changes needed.
  • [2007-02-15] Added link to publically available doc on Patch Testing.
  • [2007-02-14] Added link to Sun Java Multi Platform support offerings.
  • [2007-02-14] Added clarification to Customer actions needed for CDE.
  • [2007-02-14] Added content for JDS Linux/Solaris.
  • [2007-02-14] Added clarification on Java versions supported
  • [2007-02-14] Added supported Java versions to Sun MC to reference 1.4.2 or higher
  • [2007-02-12] Added link to Calendar Server Sun Alert 102792
  • [2007-02-08] Directory Matrix Updated
  • [2007-02-08] Added Section: Java Desktop System (JDS) and Common Desktop Environment (CDE)
  • [2007-02-08] Added Customer impact statements for Web Server, Web Proxy Server and Active Server Pages