Impacts to Business Objects Enterprise
Impacts to BusinessObjects XI R2, BusinessObjects XI R1, and Crystal Enterprise 10:
Please find the three ways unpatched BusinessObjects XI Rx products will be affected if the patch for extended Daylight Saving Time (EDST) is not applied.
- In clustered deployments it is important to ensure that all central management server (CMS) clusters have the same patches applied. If a CMS cluster has one CMS with a patched operating system (OS), and another CMS is running on a non-patched OS, the time difference will be greater than one hour. This time difference will prevent the cluster from forming when one CMS is in DST while the other is not.
- In instances where the web component server (WCS) is running on a machine with a patched OS and the CMS is running on an unpatched OS a "Run Now" command will be delayed by one hour during DST.
- Scheduled tasks will run an hour later during the extended Daylight Saving Time period.
Impacts to Crystal Reports XI R2 and Crystal Reports XI
The ShiftDateTime formula function will use incorrect DST rules, by default, if none are specified for dates after 2007.
Upon further testing two additional EDST issues affecting Crystal Reports XI and XI R2 have been identified. These issues only impact customers using the ShiftDateTime function or the Current CE User Time Zone special field.
These issues are only fixed in the CHF15_EDST patch, they are not fixed in CHF15 or CHF16. The issues are:
- The ShiftDateTime function will not return the correct time during the Daylight Savings Time extension when the Crystal Report uses Business Views
- The Current CE User Time Zone special field in Crystal Reports will not return correct EDST time when the user sets the time zone in InfoView to any time zone other than default.
If you use either the ShiftDateTime function or the Current CE User Time Zone special field, and wish to avoid the above issues, you will need to install CHF15_EDST.
Installing CHF15_EDST:
CHF15_EDST can be installed on top of MHF1, CHF13, or CHF14. CHF15 does not need to be installed to apply CHF15_EDST.
- If you have installed CHF15 you will now also have to install CHF15_EDST on top of it
- If you are planning to apply CHF16 will need to apply the CHF15_EDST patch before you apply CHF16
- If you have already applied CHF16 you will need to roll back, apply the CHF15_EDST patch first, and then reapply CHF16
- You can also elect to not apply CHF15_EDST on top of CHF15 or CHF16 and wait until CHF17 is released towards the end of March
Please note that CHF15_EDST only needs to be applied in addition to CHF15 and CHF16 if you are using the ShiftDateTime function or the Current CE User Time Zone special field.
Tomcat Deployments
We strongly recommend that deployments of BusinessObjects Enterprise on Tomcat ensure that the JDK version Tomcat is using is updated with at least JDK 1.4.2_11. Please refer to this webpage for information on the TZupdater tool from Sun. http://java.sun.com/javase/tzupdater_README.html
Attention Windows Users: Once your OS, Java, and Business Objects patches have been applied a reboot of your system is recommended.
Impact to BusinessObjects 6.5 SP3:
On UNIX, the user may find that when clicking Refresh in the All documents page in InfoView, the List Refresh Time parameter will display a timestamp that is out-of-sync with the server time by up to an hour. Since no data or functionality is impacted, the recommendation is that no patch be applied. The problem is fixed in BusinessObjects 6.5 SP4, so an alternate solution is to install CHF64 or above.
Impacts to Data Integrator
Data Integrator systems without the EDST patch may be impacted in several ways. Depending on the product version, you may encounter one or more of the issues described below. Both the core Data Integrator component and the web applications component are affected by EDST.
Core Data Integrator Component
The DST issues affecting the core Data Integrator component are corrected by retrieving date and time information from the OS, once the patch is applied. Without the EDST patch the core Data Integrator component may be impacted the following ways:
- The Daylight Saving Time (DST) change affects Data Integrator jobs that are using History Preserving transform with the option "Preserve delete rows(s) as update rows(s)" enabled. Without the EDST patch the Data Integrator engine will generate the wrong time for the to_date column. This error will begin on the second Sunday of March at 2:00a.m (i.e. March 11, 2007) until first Sunday of April at 2:00 a.m. The wrong time will also be generated between the last Sunday of October at 2:00a.m. and the first Sunday of November at 2:00a.m.
Examples of the time impacts can be found below.
Job Execution Time Time Value with DST Patch Time Value without DST Patch March 1, 2007 4:00a.m. March 1, 2007 4:00a.m. March 1, 2007 4:00a.m. March 11, 2007 4:00a.m. March 11, 2007 4:00a.m. March 11, 2007 5:00a.m. April 1, 2007 4:00a.m. April 1, 2007 4:00a.m. April 1, 2007 4:00a.m. October 28, 2007 4:00a.m. October 28, 2007 4:00a.m. October 28, 2007 5:00a.m. November 4, 2007 4:00a.m. November 4, 2007 4:00a.m. November 4, 2007 4:00a.m. - The DST change affects customers using the SMTP mail client provided by the smtp_to() function in Data Integrator. Without the EDST patch the Data Integrator SMTP client will assign an incorrect mail sent time starting the second Sunday of March at 2:00a.m. (i.e. March 11, 2007) until first Sunday of April at 2:00a.m. The sent time will also be incorrect between the last Sunday of October 2:00 at a.m. until first Sunday of November at 2:00a.m.
Web Application Components
Data Integrator now bundles a new version of the JVM that contains the EDST patch for web application components. Details of the JVM patch can be found on Sun’s website at: http://java.sun.com/developer/technicalArticles/Intl/USDST/. The date/time usage in Data Integrator’s web components are pervasive. Without the DST patch incorrect values will appear in all areas that use date/time information (such as the scheduler).
Testing Suggestions
Customers are encouraged to perform basic testing to ensure functions using date and time values from the OS reflect the new DST rules. For core Data Integrator components please check your sysdate() and systime() functions, as well as the timestamps for events in your log files. The event timestamps in your logs, adapters using time and date data types, the scheduler, and metadata integrator (when performing incremental runs) should be tested for the web application components.
The EDST patch will be available for all supported release families. Details on the impacts to each version are listed below.
| Product Version | Data Integrator Changes | Prerequisites |
| 11.7.0.1 | History Preserving, JVM upgrade | OS Patch |
| 11.5.3.0 | History Preserving, SMTP Mail, JVM upgrade | OS Patch |
| 11.0.2.20 | History Preserving, SMTP Mail, JVM upgrade | OS Patch |
| 6.5.1.30 | JVM upgrade | OS Patch |
Please note that a EDST patch will also be required for your operating system. Please contact your vendor for more details.
Attention Windows Users: Once your OS, Java, and Business Objects patches have been applied a reboot of your system is recommended.
