2007 Daylight Savings

Does anyone know if the change in the way daylight savings times start and stop will have any effect on Discoverer? We're using Discoverer 4. Is there any settings that need to be changed in Discoverer, or will operating system patches be enough for the change? I really have no idea if Disco will be affected at all, just want to ask to be safe.
Thanks

Hi there,
I’ve never really thought about this either but from my experience with Discoverer 4, we haven’t had any problems with the change in time due to daylight savings. I assume that as long as the Server hosting Discoverer has the correct time you’ll be ok as discoverer uses the Server time instead of the local clients time.
You could however test this in a development environment by setting the server’s clock and by running a few reports that have been saved in the DB or scheduled. Once run you can confirm the results and time within the EUL scheme statistics tables. Do this before and after the daylight settings and record your results. In the end you can do a comparison and see if it had any impact.
Unfortunately I haven’t got access to discoverer at the moment, but would be grateful if anyone that has tested this could share their results.
Many thanks,
Lance

Similar Messages

  • 2007 Daylight Savings Time Changes

    What, if any, effects will the 2007 changes to US daylight savings time have on the operation of the LabVIEW 7 Express development environment and deployed applications created with it?

    I believe the answer depends on the OS the application runs under.
    If MS has there act together and the machine in question has recieved updates, there should be no issue.
    If you are running Unix (or a variation o such), a patch must be applied (at least that was the story my wife gave for working all night Saturday night).
    I can not answer this Q for Mac or LV-RT running under Pharlap.
    Ben
    Message Edited by Ben on 02-27-2007 10:24 AM
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • 2007 Daylight savings time - Oracle 9.2

    Hi All,
    My Oracle database runs on Windows 2000 Advanced Server. I have followed Microsoft instructions to update the Daylight Savings Time to new settings. Given this, will I need to apply Oracle patches ?
    Thanks for your help,
    P.

    You will need to patch Oracle, check this blog for more info.
    http://blogs.oracle.com/otn/stories/storyReader$367

  • DST-2007 Daylight Savings Time Patches for MAC OS

    I have found Daylight Savings Time patches for other platforms.
    Is there a patch for Daylight Saving Time for MAC OS?
    Thanks.
    Bev

    markpb91 wrote:
    Coffs Harbour, northern NSW along the coast. So I'm on Sydney AES time.
    Beautiful part of the world! I have under Date and Time in System Preference marked as such
    Date and Time    South Asia (have set automatically unticked)
    Then Time Zone set for Australian Eastern Daylight saving time
                                       Melbourne - Australia    (I'm in Ballarat)
                                       With set time automatically up the top unticked
    They are the settings I have always used and my computers have always reverted to and from Daylight savings (except of course I'm in Queensland, Then I have to reset my location and remember  to set it back.
    Other than that if may come down to trashing your pref file for date and time.
    Good Luck

  • 2007 US Daylight Savings change time zone support in JDK 1.3

    Sun has supported the 2007 US Daylight Savings change in recent versions of its JDKs 1.4 and 1.5. It has made partial Daylight Savings changes to JDK 1.3, but it's not a complete implementation like in 1.4 and 1.5, because there is no support for past/future Daylight Savings rules, only a single current set of Daylight Savings rules per time zone.
    Our Java application (running in the America/New_York time zone) seems to be doomed, because the likelihood of upgrading to JDK 1.4/1.5 seems slim (we have to upgrade a third-party product first and success is seeming more and more remote), and Sun claims to be unable to fully implement the Daylight Savings change in JDK 1.3.
    If any Sun Java staff can explain the reasons for being unable to implement the change in 1.3 (or at least some kind of workaround that an individual JVM user could enable), please fill me in. Any pointers on cleanly setting up a custom workaround would be valuable too.
    If there are other Java users in the same situation, please fill me in on your own plans if you can. Is anybody trying to pressure Sun or other vendors for a solution? Is anybody writing their own custom workaround?
    More details....
    What we really need is for the default TimeZone in JDK 1.3 (America/New_York on our machines) to work regardless of whether the date/time being checked is pre-2007 or post-2007. In particular, getOffset and inDaylightTime should work for both 2006 dates and 2007 dates. The JDK should return the correct values for 2006 dates, as well as the correct values for the 2007 US DST extension dates (03/12/2007-04/02/2007 and 10/29/2007-11/05/2007). This would enable parsing and formatting using SimpleDateFormat to work correctly as well. The TimeZone and SimpleDateFormat APIs are used throughout our application.
    JDK 1.3.1_19 has an interesting workaround that depends on the current system time. Prior to Jan 1 2007, it will handle 2006 dates correctly but 2007 dates wrong. After Jan 1 2007, it will handle 2007 dates correctly but 2006 dates wrong. Either way, it is always wrong for some dates.
    JDK 1.4.2_13 and 1.5.0_09 both handle 2006 and 2007 dates correctly.
    If JDK 1.3 will never work for 2006 and 2007 dates, then I am contemplating two workarounds:
    1. Set the default TimeZone to a custom implementation as soon after JVM startup as possible.
    2. Avoid the default TimeZone entirely, changing our application code to rely on explicit custom TimeZones.
    Prior related Java Forum topics:
    * http://forum.java.sun.com/thread.jspa?forumID=31&threadID=645874 (Java Essentials - Java Programming) winds up referencing the JDK 1.4 patch as a solution, and there is some discussion about how future/historic dates affect applications
    * http://forum.java.sun.com/thread.jspa?forumID=481&threadID=735038 (Deploying - Java Upgrade) just talks about 1.4 and 1.5 patches
    * http://forum.java.sun.com/thread.jspa?forumID=481&threadID=717268 (Deploying - Java Upgrade) also just talks about 1.4 and 1.5 patches
    * http://forum.java.sun.com/thread.jspa?forumID=37&threadID=703214 (Specifications - Java Virtual Machine (JVM)) also just talks about 1.4 and 1.5
    Related Sun Java Bug Database bugs:
    * http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6471271 reports the same issue with 1.3.1_19 that I am seeing and the reporter makes the same clarification, that past/future dates don't work at all still. Sun seems to indicate that it will not fix this in 1.3.1, and the 1.3.1_19 "hack" is it for 1.3.1.
    * http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6391777 refers to updates in 1.3.1_18 to address Australia DST changes, and also indicates that past/future dates (or "historic" dates) won't work at all. It gives a little more rationale behind the difficulty of implementing this for 1.3.1.
    * http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4257314 refers to the fixes in 1.4 to support historic DST dates.
    Other articles:
    * Sun Java article http://java.sun.com/developer/technicalArticles/Intl/USDST/ refers to 1.3.1_18 as "resolving" the DST issue - this is misleading because the solution in 1.3.1_18 is not complete like that in 1.4 or 1.5
    * Server Side article http://www.theserverside.com/news/thread.tss?thread_id=42212 refers to fixes in 1.4 and 1.5 for the DST issue, and the discussion about 1.3 doesn't lead anywhere
    Thanks for any info or advice available,
    Jim

    Hi KBarney
    I think u have the correct data file. to make sure see the "zi" dir is backed up in ur java lib folder or not.
    if u have suspicion than run the tzupdater tool again.
    this tool must be run for each jre/java version on your machine separately.
    I tried this on 1.4.2.13 and not on 1.5.0.10. here is the result:
    C:\Program Files\Java\j2re1.4.2_13\bin>java -jar c:\tzupdater\tzupdater2006p\tzu
    pdater.jar -t -v
    java.home: C:\Program Files\Java\j2re1.4.2_13
    java.vendor: Sun Microsystems Inc.
    java.version: 1.4.2_13
    JRE time zone data version: tzdata2006p
    Embedded time zone data version: tzdata2006p
    Validating the time zone data
    Validation complete
    C:\tzupdater\tzupdater2006p>java -jar tzupdater.jar test verbose
    java.home: C:\Program Files\Java\jre1.5.0_10
    java.vendor: Sun Microsystems Inc.
    java.version: 1.5.0_10
    JRE time zone data version: tzdata2006k
    Embedded time zone data version: tzdata2006p
    Validating the time zone data
    /data/tzdata2006p.test:990: test failed: America/Managua
    /data/tzdata2006p.test:1465: test failed: America/Havana
    /data/tzdata2006p.test:1466: test failed: America/Havana
    /data/tzdata2006p.test:1847: test failed: Cuba
    /data/tzdata2006p.test:1848: test failed: Cuba
    /data/tzdata2006p.test:2024: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2026: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2028: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2030: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2032: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2034: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2036: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2038: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2040: test failed: America/Campo_Grande
    /data/tzdata2006p.test:2046: test failed: America/Cuiaba
    /data/tzdata2006p.test:2048: test failed: America/Cuiaba
    /data/tzdata2006p.test:2050: test failed: America/Cuiaba
    /data/tzdata2006p.test:2052: test failed: America/Cuiaba
    /data/tzdata2006p.test:2054: test failed: America/Cuiaba
    /data/tzdata2006p.test:2056: test failed: America/Cuiaba
    /data/tzdata2006p.test:2058: test failed: America/Cuiaba
    /data/tzdata2006p.test:2060: test failed: America/Cuiaba
    /data/tzdata2006p.test:2062: test failed: America/Cuiaba
    /data/tzdata2006p.test:2471: test failed: America/Montevideo
    /data/tzdata2006p.test:2472: test failed: America/Montevideo
    /data/tzdata2006p.test:2475: test failed: America/Montevideo
    /data/tzdata2006p.test:2476: test failed: America/Montevideo
    /data/tzdata2006p.test:2479: test failed: America/Montevideo
    /data/tzdata2006p.test:2480: test failed: America/Montevideo
    /data/tzdata2006p.test:2483: test failed: America/Montevideo
    /data/tzdata2006p.test:2484: test failed: America/Montevideo
    /data/tzdata2006p.test:2487: test failed: America/Montevideo
    /data/tzdata2006p.test:2494: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2496: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2498: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2500: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2502: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2504: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2506: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2508: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2510: test failed: America/Sao_Paulo
    /data/tzdata2006p.test:2516: test failed: BET
    /data/tzdata2006p.test:2518: test failed: BET
    /data/tzdata2006p.test:2520: test failed: BET
    /data/tzdata2006p.test:2522: test failed: BET
    /data/tzdata2006p.test:2524: test failed: BET
    /data/tzdata2006p.test:2526: test failed: BET
    /data/tzdata2006p.test:2528: test failed: BET
    /data/tzdata2006p.test:2530: test failed: BET
    /data/tzdata2006p.test:2532: test failed: BET
    /data/tzdata2006p.test:2537: test failed: Brazil/East
    /data/tzdata2006p.test:2539: test failed: Brazil/East
    /data/tzdata2006p.test:2541: test failed: Brazil/East
    /data/tzdata2006p.test:2543: test failed: Brazil/East
    /data/tzdata2006p.test:2545: test failed: Brazil/East
    /data/tzdata2006p.test:2547: test failed: Brazil/East
    /data/tzdata2006p.test:2549: test failed: Brazil/East
    /data/tzdata2006p.test:2551: test failed: Brazil/East
    /data/tzdata2006p.test:2553: test failed: Brazil/East
    /data/tzdata2006p.test:3451: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3452: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3453: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3454: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3455: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3456: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3457: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3458: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3459: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3460: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3461: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3462: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3463: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3464: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3465: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3466: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3467: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3468: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3469: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3470: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3471: time zone not found: Europe/Podgorica
    /data/tzdata2006p.test:3791: test failed: ART
    /data/tzdata2006p.test:3814: test failed: Africa/Cairo
    /data/tzdata2006p.test:3844: test failed: Asia/Amman
    /data/tzdata2006p.test:3848: test failed: Asia/Amman
    /data/tzdata2006p.test:3852: test failed: Asia/Amman
    /data/tzdata2006p.test:3856: test failed: Asia/Amman
    /data/tzdata2006p.test:3860: test failed: Asia/Amman
    /data/tzdata2006p.test:3887: test failed: Asia/Damascus
    /data/tzdata2006p.test:3908: test failed: Asia/Gaza
    /data/tzdata2006p.test:3911: test failed: Asia/Gaza
    /data/tzdata2006p.test:3915: test failed: Asia/Gaza
    /data/tzdata2006p.test:3919: test failed: Asia/Gaza
    /data/tzdata2006p.test:3923: test failed: Asia/Gaza
    /data/tzdata2006p.test:4035: test failed: Egypt
    /data/tzdata2006p.test:4901: test failed: Australia/Perth
    /data/tzdata2006p.test:4902: test failed: Australia/Perth
    /data/tzdata2006p.test:4905: test failed: Australia/Perth
    /data/tzdata2006p.test:4906: test failed: Australia/Perth
    /data/tzdata2006p.test:4909: test failed: Australia/Perth
    /data/tzdata2006p.test:4910: test failed: Australia/Perth
    /data/tzdata2006p.test:4914: test failed: Australia/West
    /data/tzdata2006p.test:4915: test failed: Australia/West
    /data/tzdata2006p.test:4918: test failed: Australia/West
    /data/tzdata2006p.test:4919: test failed: Australia/West
    /data/tzdata2006p.test:4922: test failed: Australia/West
    /data/tzdata2006p.test:4923: test failed: Australia/West
    Validation tests failed.
    -Ranjan

  • Daylight Savings Time -2007

    In 2007 when the US changes the start/end dates for daylight savings time, will Apple patch 10.4.x, 10.3.x etc?

    Apple has already patched Mac OS X 10.4 for the changes; this is included in Mac OS X 10.45 and newer.
    (17177)

  • Daylight Savings Time 2007 - firmware upgrade ?

    In 2007 the start and end dates are going to be different for Daylight Savings Time. As a result, servers are going to need to be patched. Here is a related link I came across:
    http://sunsolve.sun.com/search/document.do?assetkey=1-26-102617-1
    My question is, how do I know whether or not my firmware (PROM) needs to be updated too ? I have searched and have not found a lot of information on the topic of the firmware. Does anyone have any good links or pertinent information on whether the firmware would need to be updated or not ? I have several Netra T1's, Sunfire V480's, and my Sunblade 100 workstation that I am concerned about. Here is the OBP level from one of my V480's that is on Solaris 8: OBP 4.6.8 2002/09/04
    and here is the OBP from a V480 on Solaris 9: OBP 4.10.14 2003/11/19.
    Thanks for any information.

    The platforms mentioned in the Sun Alert 102617 that you linked above,
    are all Sun Fire Midrange Server systems.
    Their "firmware" is a part of a completely different sort of of architecture.
    Their system controllers are a tiny computer, with its own OS, inside the Sun Fire system.
    That Real Time Operating System (RTOS) that runs on the SC's has its own
    time-of-day function that is independant of whatever Solaris gets installed
    to whichever domain or domains you configure to the computer.
    Thus the need for the Sun Alert, separate from any TOD discussion for Solaris..

  • Daylight Savings Changes 2007

    Daylight Savings time will be altered in 2007 as seen in http://geography.about.com/cs/daylightsavings/a/dst.htm
    Is Coherence certified to handle these changes? We have already found issues in the OS and JDK that need to be patched.

    Coherence will correctly handle daylight savings changes once the JDK has been patched.
    Without the JDK patch, only the Coherence logging function will be incorrect, in that the logged messages will reflect the incorrect (unpatched) "timezone".
    Coherence has very careful handling of "wall clock time" functionality to avoid being impacted by network time daemons, system clock irregularities, time zone shifts, etc.
    Peace,
    Cameron Purdy
    Tangosol Coherence: Data Grid and Clustered Cache

  • COREid and Daylight Savings Time for 2007

    Do COREid or any of its components require any special fix in order to comply or function properly with the new Daylight Savings Time for 2007?
    Background:
    In August of 2005 the United States Congress passed the Energy Policy Act,
    which changes the dates of both the start and end of daylight saving time
    (DST). When this law goes into effect in 2007, DST will start three weeks
    earlier (2:00 A.M. on the second Sunday in March) and will end one week later
    (2:00 A.M. on the first Sunday in November) than what had traditionally
    occurred.
    Thanks,
    Craig
    Message was edited by:
    user557097

    We have experienced many problems with DST and COREid in the past; most of them resulting in hung Access server and unavailability. I don't know if it's because we have components distributed across multiple time zones or what. Our plan is to have someone available at the time change to cycle the services (and maybe the server as a whole) and do a health check after the fact. I hope this helps.
    --Aaron                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Any imapct on MS JVM due to Daylight savings changes in 2007

    Is there any imapct on MS JVM due to the Daylight savings changes in 2007.

    I don't know. What did Microsoft support tell you when you asked them?

  • Update for the new Daylight Savings Time on March 11, 2007

    Is there and update for the new Daylight Savings Time on March 11, 2007. the government changed it for this year. iCal won't let you modify the event.

    Macspacedog,
    Welcome to Apple Discussions.
    As you have noticed, you cannot modify a subscribed calendar.
    Since your system has been updated to 10.4.8 it will recognize the change, but the current Holiday Calendar available through Apple-Mac OS X-iCal-Library has not yet been updated to reflect the change.
    If you want to subscribe to a different calendar, it appears that the iCalShare Holiday Calendar has been properly updated to reflect the correct Daylight Savings time.
    ;~)

  • Daylight Savings Time Change Mar-2007

    Is this years new date for DayLight Savings Time going to affect my WRT54G v3.1 router?  My firmware is 4.30.5.
    Also, does anyone know why the opening admin page for my router say I have a WRT54GL?

    Versions 1 - 4 and GL's use the same firmware because they all have the Linux operating system.
    The new release firmware for versions 1 to 4 is 4.21.1  If there is no fix for the new DST in 4.30.x it might be in the new release.

  • Iphone calendar off by 1 hour after daylight savings

    i have my iphone synced to my outook 2007 through an exchange server. after daylight savings this weekend, all of my appointments are now off by 1 hour. they are all correct in my outlook and on the exchange server (verified by web browser). i've tried deleting the exchange account from the phone and reinstalling, but that doesn't work. also, when i try adding a new appointment on my iphone, it shows up off by one hour in the exchange calendar. my iphone is currently showing the correct time.
    anyone know what the heck is going on?

    I also had success using this method, from above:
    On iPhone, go to Settings>Mail, Contacts, Calendars.
    Scroll way down to Time Zone Support. Note that it's listed as GMT-4. Turn slide button to OFF, then back to ON. Note that it automatically goes to Washington, DC (GMT-5).
    Calendar appointment times now correct.
    Time on the iPhone updated automatically for daylight savings, but the Time Zone Support function didn't make the one-hour shift; they ended up out by an hour from one another. Forcing Time Zone Support to refresh its settings was all that was needed.

  • Energy Act of 2005 and Daylight Savings Time

    We currently use Sun Studio compilers. We use the embedded tools.h RogueWave libraries. The Energy Act of 2005 changes the dates for Daylight Savings Time starting in 2007. Will there be any patches from Sun to handle this? We currently use RWZoneSimple which is extensible, but we were hoping for an update from Sun.
    Thanks in advance. Sorry if this has been covered, I just couldn't find anything.
    Further Reading:
    http://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005

    The RW Tools.h++ library that comes with Sun Studio has been updated with the new DST rules. I don't think the patches have been released yet.
    If you have a service contract with Sun, you can get a pre-release version of the patch via your support channel.
    Otherwise, check the Sun Studio patch page from time to time
    http://developers.sun.com/sunstudio/downloads/patches/index.jsp
    Look for a C++ compiler patch that includes a fix for bug 6456479.
    RW Tools.h++ does its own DST calculations. Other libraries rely on the Solaris functions in libc. Patches for Solaris are available now as follows:
    S10 - 118833-24(sparc), 118855-19(x86)
    (The fix is included in S10u2.)
    S 9 - 112874-34(sparc), 114432-24(x86)
    S 8 - 108993-62(sparc), 108994-62(x86)

  • JDev log times and Daylight Savings

    Nothing major.
    I've noticed that the log messages appearing in JDev are not respecting my daylight saving time. Log times are appearing as 1 hour earlier than my computers time.
    My platform is WinXP with Western Australian Daylight Savings patch applied.
    e.g. at 14:14:56
    3/02/2007 13:14:56 oracle.jsp.logger.JspMessages infoProviderURIUsed
    INFO: Using the ProviderURI /mdssys/ViewController/public_html/MyContent.jspx that is returned from custom provider for processing requests.
    3/02/2007 13:15:23 oracle.jsp.logger.JspMessages infoProviderURIUsed
    INFO: Using the ProviderURI /mdssys/ViewController/public_html/MyContent.jspx that is returned from custom provider for processing requests.

    As a matter of interest, do you get the same when if using JDK 1.5.0_07
    If you've Metalink access, see Note 397281.1
    Also, see: JDeveloper 10.1.3.1 Daylight Savings Time patch
    PS
    If you haven't already, you can also post discussions to the JDeveloper forum:
    JDeveloper and ADF

Maybe you are looking for

  • Using apple tv

    How can i play movies from my imac(2008) through apple tv which are not in my itune library

  • Size in JTable

    Hi! I have a little problem with JTables. If I want to show more than 20 files (it�s 20 because of the size of the window, this number is not important), it only shows a certain number of them, the others don�t appear. The autoscrolls field is "true"

  • Pretest Quiz and Quiz branching.  Not working.

    I have edited pretest actions correctly (per the tutorial) to route the learner back to the beginning of the slides if they miss 2 out of 3 pretest questions.  However, when 2, or all 3 slides are answered incorrectly it does not route them back.

  • Deleted notes from g mail and all notes disappeared.How do I retrieve.

    I was purging my g mail on my i pad and removed notes. I don't want the notes in g mail - only in notes. Before I knew it, my notes were completely gone. So I turned wi fi off on ipad and ipod so that i could save the notes in i pod and perhaps save

  • It is possible ssh from a router to another, to its ipv6 link-local address?

    Hi  R1 and R2 are connected by serial links, with IPV6 address global unicast and link-local every link. I can do ping between them. When I do ping to link-local address next router, I need to specify outgoing interface, ping is succesful. However I