SAP Landscape Management 3.0, Enterprise Edition

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 Information published on SAP site and create a POST-stop hook or enter it in the StartProfile.

  • The instance status is Running 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 Start of the navigation pathSetup Next navigation step Settings Next navigation step EngineEnd of the navigation path.

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

Stop Operations

Description

Stop

Stops an instance.

Possible shutdown options:
  • Soft Shutdown

  • Hard Shutdown

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:
  • Soft Shutdown

  • Hard Shutdown

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 Options

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

  1. Choose Operations.
  2. Choose Systems from the tabs.
  3. From the Operations dropdown for the instance, choose Stop (including unprepare if possible) Stop (including unprepare if possible).

    To stop and unprepare multiple instances at once, choose Start of the navigation pathMass Operations Next navigation step Stop (including unprepare if possible)End of the navigation path and ensure that the entities on which you want to execute the operation are displayed and selected.

  4. Optional: SAP Landscape Management checks if the host assigned to the instance meets the requirements of the instance. These requirements include RAM, SAPs, and so on. To ignore this host check, select the Ignore Host Check checkbox.
  5. Optional: SAP Landscape Management checks if intersystem dependencies are defined, and either performs the necessary action or prompts you to decide whether to proceed with the operation. To ignore any intersystem dependencies, select the Ignore Intersystem Dependencies checkbox.
  6. Optional: Select the Set Note checkbox and enter a note that is to be displayed in the Description column of the instance.
  7. Choose Execute.

Results

Stop
  1. Stops the instance.
  2. Sets the instance status to Not running Not Running.
Unprepare
    • For database instances:
      1. Unregisters the database from the operating system.
      2. Detaches the database from the host. That is, stops the database listeners, if necessary.
      3. Creates configuration files required for an attach process during a prepare operation.
    • For SAP instances that do not represent a database:
      1. Stops the instance agent
      2. 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:
      1. Performs necessary actions to unregister the instance on the host.
      2. Calls operation acc_<custom instance type>_detach.
      3. No processes of the custom instances are running.
  1. 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.

  2. Calls the storage adapter or virtualization adapter to unprepare the IP addresses.
  3. The instance status is Initial Initial.
  4. Receives service port bindings needed for an attach operation.

Next Steps