How to Prepare SAP SYSTEM for Daylight Saving Time Change

On Sunday 2016, November 6th  at 2:00 AM Local time (where servers reside, here its ET), annual Time Change to daylight savings will take place.

Daylight Saving Time Details:

YearDST Start (Clock Forward)DST End (Clock Backward)
2015Sunday, March 8, 2:00 AMSunday, November 1, 2:00 AM
2016Sunday, March 13, 2:00 AMSunday, November 6, 2:00 AM
2017Sunday, March 12, 2:00 AMSunday, November 5, 2:00 AM

During this time of one hour “Fall Back” on the clock, as is our Basis team best practice (SAP Note #7417, #102088 and others) we intend to gracefully shut down all Production applications prior to 2:00 AM, at which time the “fall back” happens that will revert back clock time by one hour.  We would then wait for clock time to advance past the “new” 2:00 AM Local time.  And start from 2:05 AM EST will bring up applications.

The benefit of doing this, is that any running processes, batch or otherwise, that could potentially imprint out of sequence time stamps, would be quieted during this period of time .Also to avoid any data inconsistency for this double hour.


We wanted you to be aware of this event coming up and what Basis intends to do in response to it, in the interests of avoiding any potential for data integrity issues due to fall Time Change.

Detail information of activity:

  1. All the Application and DB should be down before 2:00 AM ET, so need to start bringing down the system at least from 1:00 AM ET
  2. Once the time will change at 2:00 AM PT to NEW 1:00 AM PT, we will wait for 1 hours’ time to  reach the clock again to NEW 2:00 AM PT, to avoid any duplication.
  3. We will bring the Systems up at 2:05 AM PT (NEW TIME)

Before Clock reset –>   1:00 – 1:59 (Stop SAP and Database)

Clock Reset 2:00   –>   1:00

After Clock reset  –>    Ideal Period (1:00 — 2:00)

After Clock reset  –>   Start SAP and Database After 2:05 (NEW TIME)

*Here all timings are in ET and AM.Check timing as per your time zone.

Leave a Reply

Your email address will not be published. Required fields are marked *