Scheduled reports running an hour early

scheduling XI Scheduler
1

Hi,

I have some BOXI reports scheduled and it to ran an hour early last weekend (only once) . The webshere, Scheduler server and even BOXI id from which this is scheduled is in UK zone ( no clock change).

Though there was a clock change in states ( US) that day but I do not see any link :roll_eyes:
Any clue why this would have happened? The database also has a timezone of UK. :?

Amy_Vikram :india: (BOB member since 2011-10-15)

2

[Moderator Note: Moved from Broadcast Agent (BCA) to XI Scheduler]

Marek Chladny :slovakia: (BOB member since 2003-11-27)

3

Search here on BOB for “DST”; there are a bunch of existing topics.

joepeters :us: (BOB member since 2002-08-29)

4

Thanks…So basically what I understand is this is a Bug for BOXIR2 :shock: and hopefully resolved for BO 3.1 ( Did not face any issue for 3.1 end till date).

And yes, the timezone setting is set to locale and its in sync with scheduler.

The link-up what I do not understand here is that the clock change was in US when this happened and this infra/scheduler is based in UK where the planned clock change is in this month end (31st March). :roll_eyes:

Can someone please let me know the following-

  1. Anyone having a idea how this is linked ( to note- even all applications are hosted in UK) :frowning:
  2. How does this DST issue gets rectified ( 2 answers I got is on its own when BO gets in Sync and rescheduling the reports) :crazy_face: Any other options?

Amy_Vikram :india: (BOB member since 2011-10-15)

5

What I know now that there existed a bug for the older versions of Business objects with DST (Daylight saving setting) on the system and was planned for a fixed later by SAP. I can confirm that this issue exists even in BO version 3.1 . An Article- 1404484 is there from SAP.

Cause stated:-this is due to incorrectly set Timezone(TZ) setting on Unix/Linux server, or one not defined in POSIX format.

Also to note - Because this issue is due to incorrect timezone configuration, this issue can occur even if a Daylight Savings Time switch should NOT have occured in your local region

What I feel from my end is that the scheduled reports are landing on a particular websphere server (which is in cluster ) and a standard Timezone(not the DST )is set on these Linux boxes and could be very much a reason for this. It may be possible that when again this is switched to standard one , this issue wont re-occur.

Amy_Vikram :india: (BOB member since 2011-10-15)

6

It affects BO installed on Windows too; not just UNIX.

There are two components to the problem – one in Tomcat and one in BOE. Both need to be corrected.

Early versions of XI3 were affected. I believe it was fixed in SP4 (definitely fixed in SP5).

This thread has a ton of information on this subject.

Joe

joepeters :us: (BOB member since 2002-08-29)

7

Just got an update -

"This issue in part is not caused by BusinessObjects, but moreso by the Java engine supplied byu Oracle.
To explain this odd behaviour, I need to give a slight history lesson.

Historically, the US performed their time change inline with the UK. However, a few years ago, they changed and performed their time change
in the second week of March. As a result, we have a period of two weeks where the a difference in times. Normally this should not have an effect
on any schedules in BOXI, however, as mentioned before, the issue is the result of the version of the Oracle Java engine used by BOXIr2.
In most instances, there are never any issues on BOXI environment.

There is a tool provided by Oracle which updates the Timezone information for the Java engine to accomodate the discrepancy.

Resolution: 1. To resolve this issue, run the Java update tool on the BOXIr2 servers
2. Would suggest rescheduling the reports back to their normal time

Amy_Vikram :india: (BOB member since 2011-10-15)