Stopping and Unpreparing Systems and Instances
You can stop an instance, unmount remote memory locations from the local file system, and unbind virtual host names from the network interfaces.
Prerequisites
-
The general prerequisites for instance operations have been met.
For more information, see General Prerequisites for Instance Operations.
-
When you unprepare systems and instances, SAP Host Agent executes the program cleanipc by default. For information on how to execute the cleanipc program when you stop a system or instance, see SAP Note 17108 and create a POST-stop hook or enter it in the StartProfile.
-
The instance status is Running.
Context
By default, SAP Landscape Management performs a soft shutdown for database instances and a hard shutdown for other instances not representing a database. You can change the default settings under .
For more information, see Configuring Engine Settings.
Ensure that you understand the difference of the following stop operations and the shutdown options before you execute the operation.
Stop Operations |
Description |
---|---|
Stop |
Stops an instance. Possible shutdown options:
|
Forced Stop |
Stops an instance while ignoring intersystem and intrasystem dependencies. You can perform a forced stop also for instances with status Unknown. Possible shutdown options:
|
Graceful Shutdown |
Stops an ABAP application server instance in the timeout specified and informs all logged users for shutdown. For more information, see Using Graceful Shutdown. |
Shutdown Option |
Description |
---|---|
Soft Shutdown |
Checks for open database connections. If any database connection is open, cancels the operation. Default option for database instances. |
Hard Shutdown |
Ignores open database connections and stops an instance immediately. Default option for instances not representing a database. |
Procedure
Results
- Stops the instance.
- Sets the instance status to Not Running.
-
- For database instances:
- Unregisters the database from the operating system.
- Detaches the database from the host. That is, stops the database listeners, if necessary.
- Creates configuration files required for an attach process during a prepare operation.
- For SAP instances that do not represent a database:
- Stops the instance agent
- Unregisters the instance agent from the operating system.
-
For Unix-like systems: Removes the agent from file /usr/sap/sapservices
-
For Windows systems: Removes the agent from the Windows service registry
-
- For custom instances:
- Performs necessary actions to unregister the instance on the host.
- Calls operation acc_<custom instance type>_detach.
- No processes of the custom instances are running.
- For database instances:
- Unbinds virtual IP addresses or unmounts the file systems configured.
If the potential SAP HANA master node is relocated and there are tenants with virtual hostnames registered on this host, they will be unbound.
When you unprepare an SAP HANA tenant database node:-
Checks if this node is a potential master host.
-
If the node is a potential master host, unprepares the virtual hostnames of all tenants which have virtual hostnames registered on the SAP HANA tenant database node.
-
- Calls the storage adapter or virtualization adapter to unprepare the IP addresses.
- The instance status is Initial.
- Receives service port bindings needed for an attach operation.
Next Steps
-
You can manage activities related to the operation that is currently running.
For more information, see Performing Operations on Activities.
-
You can view the log of all tasks involved in the process.
For more information, see Working with Logs.