
During the installation, the SAP system is started automatically with all instances on all blades.
You can use the appliancecontrol tool to manually stop and start the entire SAP system or individual instances. The procedure for doing this is described here.
In addition, there is a range of standard SAP NetWeaver ways to start and stop SAP systems, for example using the SAP Management Console. For more information, see the technical operations manual for SAP NetWeaver.
Caution
Note that the SAP NetWeaver Enterprise Search system does not work or only works in limited form if not all instances are running.
Note
If you start a dual-stack instance (AS ABAP, AS Java) individually, the system first checks whether or not the MaxDB instance is running. If the MaxDB instance is not running, the system starts it automatically before starting the dual-stack instance.
Task |
Command/Option |
|---|---|
List all blades and the instances that run on them. |
appliancecontrol list |
Activate the graphical log viewer to display the results of a command in a tree structure.
You require an X11 display for the graphical log viewer. End of the note. |
Add the —v option to a command.
appliancecontrol —v start-all End of the example. |
Stop all instances. |
appliancecontrol stop-all |
Start all instances. |
appliancecontrol start-all |
Stop individual instances. |
appliancecontrol stop <instance> |
Start individual instances. |
appliancecontrol start <instance> |
Stop all instances completely, including the sapstartsrv service.
A complete stop is necessary if you want to move instances from one blade to another. End of the note. |
appliancecontrol complete-stop all |
Start all instances completely, including the sapstartsrv service. |
appliancecontrol complete-start-all |
Stop individual instances completely. |
appliancecontrol complete-stop <instance> |
Start individual instances completely. |
appliancecontrol complete-start <instance> |
Note
<instance> refers to the ID of an instance, for example TRX22, or the database ID (MAXDB).