Wednesday, 8 June 2016

01. Starting and Stopping SAP R/3




Starting and Stopping SAP R/3
Starting the SAP R/3 system involves starting the underlying database and all the SAP processes configured to run in all application servers. The type and number of processes are configurable with the start profile and the instance profile parameters. These processes might include the following:
1.    The operating system and/or network performance collectors
2.    The central system log collection process
3.    The CPIC gateway server
4.    The message server
5.    The dispatcher processes
6.    The spool processes
7.    The dialog and background processes
Starting the SAP system first requires starting the database and then the instance processes. Stopping is the opposite process: first you have to stop the instance processes and then the database background processes.
To start or stop the SAP system in a UNIX environment, you must log on as user <sid>adm, The following commands are available.
The brackets indicate optional parameters where you can choose just one from the list or none at all.
startsap [R3] [DB] [ALL]
1.    Using the command, startsap R3, only the SAP instance is started. It is assumed that the database is already running. Otherwise, the instance will not start successfully.
2.    With the command, startsap DB, only the database is started.
3.    Using startsap ALL, the system will first start the database and then the SAP instance. ALL is the fault setting and can be omitted. If the database is running, it will just start the instance.
4.    stopsap [DB] [R3] [ALL]
5.    Using stopsap R3, all the instance processes are stopped.
6.    With the command, stopsap DB, the system stops just the database. Make sure you first stop the instance processes; otherwise, the SAP processes will "hang" because no update is possible.
7.    Issuing the command, stopsap [ALL], the system stops the SAP instance and then the database. ALL is the default parameter and can be omitted.
When in distributed SAP installations with several application servers, pay attention to stopping all the instances before stopping the database, which is only located in the database server.