STARTING AND STOPPING SAP
When you start the SAP System, we simultaneously start the
System database
Application server
Respective processes
A start profile defines which processes are to be started or stopped.
This profile is automatically generated during the system installation. You can
change it later.
You can start and stop the SAP System and its database using operating
system tools. There are special scripts available to do this, or you can use
the appropriate program icons.
You can start and stop SAP instances with the Computing Center
Management System (CCMS). The prerequisite for doing this is that the database
and at least one SAP instance have been started.
Need of restart
1.To bring changes in the system
2.Migration
3.Hardware/software updates
4.Performance
5.Backup/Recovery
Procedure on windows:
1.Start the MMC on the SAP system host by
choosing Start → Programs → SAP Management Console.
2.Right-click the SAP system node and
choose Start or Stop.
All instances listed under the system node, will start or stop in the
correct order.
3.If the SAP system is installed on
multiple hosts (distributed system), you have the following options to start or
stop your system:
·
You start or stop the SAP instances using the
MMC on each host.
·
You add the remote instances to the MMC
configuration to start or stop all instances from a single MMC. To do so, use
one of the following options to configure the MMC
Procedure on UNIX:
Starting the SAP System
1.Log on in UNIX as a user with SAP
administrator authorization (<SID>adm).
1.Enter the command startsap [DB|R3|ALL]
from your home directory. The following applies to this command:
·
DB starts the database system
·
R3 starts the instances and associated processes
of the SAP System (using the sapstartprogram)
·
ALL starts both the database system and the SAP
System. ALL is the default value and can be left out.
2.After you have started the database and
the central instance, you can perform other actions within the CCMS.
To check whether all application servers of an SAP System were started
correctly, start the Alert Monitor (transaction RZ20) or the Overview of SAP
Application Servers (transaction SM51)
Stopping the SAP System
1.Log on in UNIX as a user with SAP administrator
authorization (<SysID>adm).
2.Enter the command stopsap [DB|R3|ALL]
from your home directory. The following applies to this command:
·
DB stops the database system
·
R3 stops the instances and associated processes
of the SAP System
·
ALL stops both the database system and the SAP
System. ALL is the default value and can be left out.
Starting an SAP System is performed in a number of steps and
is the task of the operating system user adm
Start the database:
Before the SAP instances are started, this must have operational status. The database is therefore always started as the first step.
Start the central instance:
Next, the operating system collector SAPOSCOL is started, if it is not already active. This is a standalone program that runs in the operating system background, independently of SAP instances. It collects data about operating system resources and makes this data available through the shared memory of all SAP instances.
The central instance with the message server and the dispatcher and its work processes is then started. Only once the message and Enqueue servers are active can other instances be started, if desired.
Start other instances:
If the dialog instance is not running on the same host as the central instance, the SAPOSCOL operating system collector is first started on this host.
The dispatcher is then started with its work processes.
SAP Services:
SAPOSCOL: Collects performance data for one or more SAP instances and runs once for each host.
SAP_: Controls the SAP instances and runs once for each instance.
SAP Profiles
the specifications of the instances; that is, the type and number of processes, main memory sizes, and other options are controlled at the start of the instances using profiles. These are files at operating system level that are stored in the directory
usr\sap\mnt\sys\profile.
Start the database:
Before the SAP instances are started, this must have operational status. The database is therefore always started as the first step.
Start the central instance:
Next, the operating system collector SAPOSCOL is started, if it is not already active. This is a standalone program that runs in the operating system background, independently of SAP instances. It collects data about operating system resources and makes this data available through the shared memory of all SAP instances.
The central instance with the message server and the dispatcher and its work processes is then started. Only once the message and Enqueue servers are active can other instances be started, if desired.
Start other instances:
If the dialog instance is not running on the same host as the central instance, the SAPOSCOL operating system collector is first started on this host.
The dispatcher is then started with its work processes.
SAP Services:
SAPOSCOL: Collects performance data for one or more SAP instances and runs once for each host.
SAP_: Controls the SAP instances and runs once for each instance.
SAP Profiles
the specifications of the instances; that is, the type and number of processes, main memory sizes, and other options are controlled at the start of the instances using profiles. These are files at operating system level that are stored in the directory
usr\sap\mnt\sys\profile.
No comments:
Post a Comment