SAP Landscape Management 3.0, Enterprise Edition

Unpreparing Systems and Instances

You unmount remote memory locations from the local file system and unbind virtual host names from the network interfaces. For SAP instances, you stop and deregister the instance agent. For database instances, your detach the database and stop the database listeners.

Prerequisites

  • The general prerequisites for instance operations have been met.

    For more information, see General Prerequisites for Instance Operations.

  • The instance status is Not running Not running.

  • When you unprepare a system or instance, the SAP Host Agent executes the program cleanipc by default. For information on how to execute the cleanipc program when stopping 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.

  • Storage partner libraries are available and up-to date.

    For more information, see http://scn.sap.com/docs/DOC-42216Information published on SAP site.

Context

Procedure

  1. Choose Operations.
  2. Choose Systems from the tabs.
  3. From the Operations dropdown for the instance, choose Unprepare Unprepare.
  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

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