Startup & Shutdown of SAP System is one of the basic activities for SAP Administrator. Following is sample procedure to stop & start SAP System. The procedure may vary if you are using Clusters or different operating system.
- Prepare a checklist and update while shutdown and startup of all the servers for your record.
Shutting down SAP Instance
- Send notification to all users from SM02 in advance.
- Check the Application instances available and get the Instances and application servers’ list. This may be got from transaction SM51.
- Before shutting down the Application instances, verify that no users are logged in (transaction AL08), and no background jobs are active (transaction SM37).
- Log into the appropriate server at the Unix level using your login id and password and then go to adm.
- Ensure that no backup is running for SAP database.
- Shut down sequence should be strictly followed as: First shutdown the Application instances and then shutdown the Central instance and followed by database instance. (The Central instance, database instance and Application instances can be seen through transaction SM51).
- Enter the following command for stopping the SAP Instance
The hostname is the name of the server on which the instance is running. The hostname is found out by giving the command hostname or uname –a at the Unix prompt.
- Stop the SAP OS Collector by issuing the command saposcol -k. This has to be done only once on every server (app or CI) even though two instances might exist.
- Verify at UNIX prompt if all the sap processes are down. (ps –eaf | grep sap).
- Check that shared memory and semaphores pertaining to adm and ora have also been released. This may be checked using the ipcs command. Remove the shared resources if they exist even after SAP and Oracle have been shutdown. ipcrm –m and ipcrm –s should be used to remove the shared memory and semaphores ( is got from running just the ipcs command)
Starting Up the Sap Instance
- Log into the database server at the UNIX level using your user id and password and then logon to the user adm.
- The startup of the SAP system is done by first starting the Oracle database then the CI and finally the application instances (could be in any order for App Instances). Enter the following command for starting the SAP Instance:
The hostname is the name of the server on which the instance is running. This will first start the database and then the CI (on the DB+CI server) else it will start the appropriate instance only (on the app server).
- Check that the instance processes start properly. Verify it as follows: for the CI try to log into SAP and for the application instances check through SM51. If the instance does not start then check the dispatcher and work process log files dev_disp and dev_w0 respectively. These reside in the directory /usr/sap///work.
- Delete the notification message from SM02 if it is still active, before releasing the system.