Skip to main content

"DST Switch" - All you need to know about Daylight Saving Time Switch in SAP

 Daylight Saving Time(DST) : DST is the practice of advancing clocks during part of the year, typically by one hour around spring and summer, so that daylight ends at a later time of the day. 



How SAP systems are affected due to DST :

Many kinds of software that deal with local time, such as the SAP system, have serious problems in this hour, because operations which use local times can fail if time does not increase continuously, and points in time can "happen" twice.

Double Hour Concept :

In many northern hemisphere countries (i.e., Europe: European Union, Russia; North America: USA, Canada, Mexico) At the end of daylight-saving period, one hour occurs twice as the clocks are put back an hour. In Europe, for example, this hour is between 2:00 a.m. and 3:00 a.m., whereas in the USA it occurs between 1:00 a.m. and 2:00 a.m.

This means that the clock will move twice in the same day from 1am to 2am. Double hour refers to the duration of the hour that the clocks traverse twice-from 1am to 2am.

 

How to handle Double hour issue in SAP:

1. Two Hour downtime method: Completely stopping the SAP system during this double hour.

2. One hour downtime method:  Let SAP system run through the double hour once. Then shutdown SAP so that it avoids going through the double hour again.

3. Zero downtime method: Slow down the time in the SAP System.


Method-1) Two-hour downtime

The first method is simple and straight forward. Simply shutdown the SAP system, for the entire duration of the double hour, and bring it up only after the double hour has passed. Thus, the SAP Kernel software does not have to deal with any possible mismatch of standard time and local time.

       1.     Stop SAP just before the double hour time.

2.     Keep SAP in stopped state for next two hours.

3.     After the daylight-saving time change, bring up the SAP when clock reaches the actual time again.


1:00   1:30   2:00   2:30   2:00   2:30   3:00    official time
-+------+-----x+xxxxxx+xxxxxx+xxxxxx+xxxxxx+x---  (X -> Downtime)

Drawback : Only drawback is larger downtime (i.e., 2 Hours)

Method-2) One-hour downtime

The second method is almost the same as the first one. However, you should adopt this only in cases where all of your SAP systems have identical local time settings.  In that case, you can reduce the downtime close to 1 hour instead of 2 hours. In practical terms, here is what you can do:

If you are using kernel 6.40 or higher, you need to set the following profile parameter according to Note 950114: zdate/DSTswitch_contloctime = off

You should use transaction RZ11 to dynamically switch the profile parameter in the active system before the "double hour".

1.      Shutdown SAP a little before 2 am(official time) before the clock is changed back to 2am(DST switch)

2.      Wait for one hour to pass and the clock moves to 3am(Official time)

3.      Bring up SAP

1:00   1:30   2:00   2:30   2:00   2:30   3:00 official time
-+------+------+------+-----x+xxxxxx+xxxxxx+x--- (X -> Downtime)


Drawback : Only drawback is 1 Hour downtime; Rather than option 1 which has 2 hour downtime.


Method-3) Zero downtime method 

In this case, you slow down the time by half by setting parameter zdate/DSTswitch_contloctime = on, during the double hour, so that the 2 hour period is treated as one hour. You can make your SAP system see a continuous time with a deviation of 30 minutes. 

Note: You should check the pre-requisites in the notes mentioned at end of this blog, before executing this method to avoid any issues.

1.      At 2am, i.e., one hour before the change of time, your SAP system clock starts running slowly at half the normal speed

2.      For the next two hours, the SAP system will run slow at half speed (No impact due to slow time in SAP, this is just a perception not real.)

3.      Hence, the double hour is observed as one continuous hour by SAP.

4.      After two hours duration, the official clock time and SAP time will match. Hence, the system will continue normally from then onwards (with both official and SAP clocks being in sync).

 1:00   1:30   2:00   2:30   2:00   2:30   3:00  official time
 -+------+------+------+------+------+------+---                     1:00   1:30   2:00   2:15   2:30   2:45   3:00  SAP time



References :

https://launchpad.support.sap.com/#/notes/7417

https://launchpad.support.sap.com/#/notes/398374

https://launchpad.support.sap.com/#/notes/950114

https://launchpad.support.sap.com/#/notes/102088

https://blogs.sap.com/2009/12/09/daylight-saving-time-and-slowing-down-the-time/#:~:text=1)%20Two%20hour%20downtime%20method,time%20in%20the%20SAP%20System.


Comments

Post a Comment

You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/enUS/b3/903925c34a45e28a2861b59c3c5623/content.htm?no_cache=true How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : sap-perf.ca Let's discuss the WORKLOAD MONITOR By D

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

SAP system migration blog series - part 1: migration overview

Summary : This blog is part 1 of the blog series on SAP system migration. In this blog, we will provide overview about SAP migration, types of migration, their differences and usage scenario. SAP migration overview :   As the Greek philosopher, Heraclitus, said: “change is the only constant.” Same goes within SAP world too, often customer have to change the SAP systems along with its underlying components to meet the changing requirements, be it change from old hardware to new one, changing operating system, database. This change in SAP system components (DB, OS or Hardware) is termed as migration. Before we go into details of migration, let’s understand architecture of a typical SAP system.   An SAP system consist of SAP application instances, running on database (DB), hosted on operating system (OS), provisioned on hardware. Change in any one or more of these underlying components (DB, OS or hardware) warrant us to perform migration. Types of migration:   Broadly, there are two types

SAP HANA System Replication - Operation Mode & Replication Mode

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out what is hana system replication and how it basically works. If you haven't gone through that blog, you can checkout link In this blog we will be talking about the replication modes and operation modes in hana system replication. So let's get started. When we setup the replication and register the secondary site, we need to decide the operation mode & replication mode we want to choose for replication. For now we won't focus on setting up replication as we'll cover it in our next blogs.  Operation Modes in Hana System Replication: There are three operation modes available in system replication: delta_datashipping, logreplay and logreplay_readaccess. Default operation mode is logreplay. 1. Delta_datashipping: In this operation mode initially one full data shipping is done as part of replication setup and then a delta data shipping takes place occasionally in addition to cont

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set

Complete Guide : XPI Inspector Tool

Content of this blog :           What is an XPI Inspector Tool ? Why XPI Tool is used ? XPI standard URL How to check XPI Tool version ? How to Install/Update XPI version using TELNET How to Use XPI Tool ? References – SAP Notes What is XPI Inspector tool ?          -    XPI Inspector is a diagnostics web application developed by SAP that collects logs and debug traces from various PI components in a very simple way and is useful for SAP PI consultants, developers, and administrators to get more insights on an issue. Why XPI is used  – 1.  Used to collect traces and logs from Messaging system or XI module. 2. Used to collect the related information to solving the issues or improving the PI or PO systems’ performance. 3. Using XPI Inspector application you will be able to collect a lot of information about your system that will help you to learn about problems in the past, to analyze new and detect such at an early stage. 4. Performs certain number of configuration checks, such as SSL c