BI Platform uses outdated DST settings and reports appear to run an hour early or late

BI Platform uses outdated DST settings and reports appear to run an hour early or late

  • Recurring schedules may appear to be running an hour early, or late in history page
  • Reports that are scheduled to Run Now show Completion Time one hour ahead or behind the current time
  • Daylight savings time in the user’s region may have changed to start/end at a different time, or to not take effect

Environment

  • SAP BusinessObjects BI Platform 4.1
  • SAP BusinessObjects BI Platform 4.2

Cause

  • The JVM running the Web Application Server has incorrect daylight savings time information

Resolution

The default Tomcat that is bundled with the BI Platform runs using the SAP JVM. The policy for updating timezone information for this is described in SAP Note 1367871

In order for the correct daylight savings time adjustment to take place, the Java Virtual Machine (JVM) must be updated to one which includes updated timezone information from IANA

Option 1: Updating Tomcat to use an updated JVM

  1. Download an updated JVM which is listed in the SAP Product Availability Matrix for the corresponding web application server
  2. Follow KBA 2504606 to change Tomcat to use the new JVM
    • If using Oracle Java, the Oracle Timezone Updater Tool can be used to update the JVM timezone information without updating the JVM. This tool does not work with SAPJVM.

Option 2: Updating BI Platform

  • The SAP JVM is periodically updated with new SP releases of BI Platform and can include updated timezone information – See KBA 2112338 for more information

Option 3: Modifying timezone file(s) included with the JVM

Warning: These instructions are provided as-is. In the event of issues arising from these instructions, any changes must be reverted before SAP can support the installation. SAP does not support any modifications or updates to SAP JVM that are not provided through the standard maintenance process.

Java 6:

  1. Download the latest SAPJVM 6.1 from the support portal
  2. Stop Tomcat, and any other process using the JRE
  3. Rename <tomcatjvm>/jre/lib/zi to <tomcatjvm>/jre/lib/zi_old
  4. Copy the <SAPJVM6.1>/jre/lib/zi folder to <tomcatjvm>/jre/lib/zi
  5. Start Tomcat

Java 8:

  1. Download the latest SAPJVM 8.1 from the support portal
  2. Stop Tomcat, and any other process using the JRE
  3. Rename <tomcatjvm>/jre/lib/tzdb.dat to <tomcatjvm>/jre/lib/tzdb.dat.old
  4. Copy the <SAPJVM8.1>/jre/lib/tzdb.dat file to <tomcatjvm>/jre/lib/zi/tzdb.dat
  5. Start Tomcat

See Also

  • SAP KBA 2504606  – Upgrading the default BI Tomcat JVM [How-To]
  • SAP Note 1367871 – Timezone updates for SAP JVM
  • SAP KBA 2112338 – List of Bundled Tomcat and JVM versions shipped with each (support pack) SP of SAP BusinessObjects Business Intelligence 4.0/4.1/4.2

Be the first to comment

Leave a Reply

Your email address will not be published.


*