Skip to main content

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 within a client/server environment. An instance runs and manages the application which has to be installed on the server.

An SAP system can consist of one or more instances, such as an SAP system with a single instance with only one central server or a client/server system with two or more separate instances. Basically, System is a collection of instances like CI, CS, AI, DB etc which can be on one server or multiple servers. A system also contains other processes which manage these instances.

A BIT ABOUT SAPSTARTSRV:

In Linux, each SAP instance is managed by a service/daemon named 'SAPSTARTSRV'. Without starting this service, you can't start/stop the instance.

So before starting/stopping the sap system, you have to make sure that the SAPSTARTSRV service is running.

CHECKING STATUS OF THE INSTANCES:

First you should check the status of the instances using the GetProcessList function of sapcontrol.

sapcontrol -nr <instance-no> -function GetProcessList

In the above image, you can see that both the instances are running.

STARTING/STOPPING AN SAP SYSTEM:

Stopping an SAP system

To stop the whole system, you have to use the StopSystem function of sapcontrol.

Here, you just have to provide only one instance number. The other related instance will be stopped automatically.

You should wait for 3-5 minutes to let system stop completely before checking the status.

sapcontrol -nr <instance-no> -function StopSystem


In the above image, you can see that both the instances have been stopped successfully using only one command.

Starting an SAP system

sapcontrol -nr <instance-no> -function StartSystem

Similarly, to start the whole system you have to use the StartSystem function of sapcontrol.

Here also, you just have to provide only one instance number. The other related instance will be started automatically.

You should wait for 3-5 minutes to let system start completely before checking the status.

In the above image, you can see that both the instances got started successfully using only one command.

Directly Restarting an SAP system

sapcontrol -nr <instance-no> -function RestartSystem

Note: You can also provide following options after StartSystem/StopSystem command:

[ALL|SCS|DIALOG|ABAP|J2EE|TREX|ENQREP|LEVEL [waittimeout in sec] [softtimeout sec]]

These options allows you to start/stop specific type of instance.

STARTING/STOPPING AN SAP INSTANCE:

Above process was about starting/stopping the whole system. Now we will see how to start/stop the individual instances.

Stopping an SAP instance:

To stop the individual instance, you have to use the Stop function of sapcontrol.

Here, you have to provide the respective instance number of the instance. The other related instance will not be stopped automatically. You have to stop it using same command with the instnce number of other instance.

sapcontrol -nr <instance-no> -function Stop

Starting an SAP instance:

Similarly to start the individual instance, you have to use the Start function of sapcontrol.

Here also, you have to provide the respective instance number of the instance. The other related instance will not be started automatically, you have to start it using same command with the instnce number of other instance.

sapcontrol -nr <instance-no> -function Start

SAPSTARTSRV SERVICE AND TROUBLESHOOTING:

Sometimes we may face issues while starting/stopping the syatem or checking status of the instances.

In order to fix those issues, we may need to start/stop the SAPSTARTSRV service.

So, let's see how to start/stop the SAPSTARTSRV service.

Stopping SAPSTARTSRV service:

We will first check whether the SAPSTARTSRV service is running or not using the ps command.

Now we will stop the service and check for the running services.

sapcontrol -nr <instance-no> -function StopService

As you can see in the above image, the SAPSTARTSRV service has been stopped for instance 00 .

Starting SAPSTARTSRV service:

While starting the SAPSTARTSRV service, it's mandatory to specify the SID of the system.

sapcontrol -nr <instance-no> -function StartService <sid>


Common issues that you may face:

Fail: NIECONN_REFUSED

This issue comes when your sapstartsrv service is not running for the instances. To resolve this issue, you just need to start this service.

For the demo purpose, we will intentionally stop the sapstartsrv service for instance 00


The above image shows that two sapstartsrv processes are running, one for each instance.


As you can see in the above image, sapstartsrv has been stopped for instance 00.

Now if we'll try to start/stop the system or get instance status, it will throw below error.


After starting the SAPSTARTSRV service, you can see in the below image that system has been started successfully without throwing an error.

Process of an instance is in "Running but not responding" state

In this case you need to stop the saptartsrv services and restart the service and the instances.

Comments

  1. Below is the sequence to start/stop SAP system,
    Start : sapstartsrv --> ASCS --> CI
    Stop : CI --> ASCS --> sapstartsrv

    Hope it helps and correct me if I am wrong ;)

    ReplyDelete
    Replies
    1. Thanks for mentioning this.
      But when we talk about SAP system, we should consider DB as well
      Your sequence is correct for application when u are starting individual instances.
      Sequence depends on the available instances in the system.
      One more point to note down here is, it's not necessary to stop Sapstartsrv while stopping a system.

      Delete
    2. I wanted to add the same point as Sachin Agrawal has already mentioned. Yes, you never have to start or stop sapstartsrv, as it is an automatic process taken care of by the OS. Your manual SAP "System" start stop sequence should be -
      Start: ASCS / SCS --> DB --> PAS --> AAS
      Stop: AAS --> PAS --> DB --> ASCS / SCS

      Delete
    3. As per my knowledge sequence is:
      Start - DB -> ASCS/SCS -> PAS -> AAS
      Stop - AAS -> PAS -> ASCS/SCS -> DB

      Delete
    4. Sachin is correct.

      Delete
    5. sachin is correct

      Delete
  2. Good blog
    Thanks for sharing

    ReplyDelete
  3. Hello
    Can you please make one blog on instance PAS CI CS ERS DI etc
    And sequence of stopping it

    ReplyDelete
  4. Very good and clear in understanding

    ReplyDelete
  5. Please note that stop and start commands are all Asynchronous.
    On some commands you can add the "wait" option with a timeout.
    This will cause sapcontrol to wait and only return when the operation is completed or when the timeout is hit.
    You may have noticed for example, that "HDBStop" will call sapcontrol with the "wait" option and it will wait for HANA to stop.

    Regards
    Darryl

    ReplyDelete
  6. After a long time, I read a very beautiful and very important article that I enjoyed reading. I have found that this article has many important points. Thanks .pls visit our website tools for pc.

    ReplyDelete

Post a Comment

You might find these interesting

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

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

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

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

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.

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

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

ABAP Dumps Analysis

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants. Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps. Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP. You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22 How to correct the error ? Hints are given for the keywords that may be used to search on the note system. Gather Information about the issue  Go to System > Status and Check the Basis SP level as well as info

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