The SAP system may need to be stopped due to maintenance purposes. These include activities such as:
• Taking an offline database backup
• Upgrading the SAP kernel
• Activation of modified profile parameters
• Upgrade of the SAP instance
• Restarting due to system performance issues
Sequence of Stopping an SAP system
• Stop all Dialog Instances (Application Servers) one by one (there is no sequence to be followed here).
• Stop the Central Instance.
• Stop the Central Services Instance if it is on a separate host other than the Central Instance.
• Finally, stop the Database Instance.
Checks to be performed before shutting down.
2. It is a best practice to post a message on the SAP system informing the active users about the decision to shut down the system. You can create a system message using transaction SM02.
3. Check for all users using AL08.
• SM04 command will show only the users logged onto the particular dialog instance. To check for all users across all instances , whether it be central or dialog , use the global command AL08.
4. Check for active Background Processes in SM50.
• Check if there are no critical background jobs running before shutdown.If there are such jobs , identify the job owner and inform them about the shutdown reasons. Also plan to restart the jobs after the system is up and running.
5. Check for Background Jobs in SM37 (Currently Active Jobs)
• Check using SM37 , for released , ready and active jobs. During the course of shutdown , the active and just released jobs might fail , and cause inconsistencies in transaction processing. If so, speak to the Job owner and ask them to reschedule the jobs or cancel the active ones.
• Execute report BTCTRNS1 to stop all released status job. To release back, you can execute report BTCTRNS2 . Steps can be referred here.
6. Check for updates in SM13
• It is important to check if there are any open updates pending. If there are any open updates , check the logs and trace files to identify the reason for the delay. In many cases , the updates may be pending because of excessive database activities.
7. Now you can proceed to stop the SAP ABAP system if all the above requirement achieved.