SAP Landscape Management 3.0, Enterprise Edition

Starting Including Preparing Systems and Instances

You bind virtual host names of an instance to network interfaces, you mount remote memory locations to the local file system, and then you start an instance.

Prerequisites

  • The general prerequisites for instance operations have been met.

    For more information, see General Prerequisites for Instance Operations.

  • The instance status is Initial Initial.

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

  • Optional: You have specified a preferred host.

    For more information, see Setting a Preferred Host for an Instance.

  • You have ensured that all instances on which your current instance depends are running.

  • You have unprepared database instances using SAP Landscape Management before performing a prepare operation. During an unprepare operation, SAP Landscape Management writes installation and configuration information needed for attaching the database.

    For more information, see Unpreparing Systems and Instances.

  • The virtual host names can be resolved on the target host.

  • Operating system users exist with the same passwords as they have on the target host. On UNIX, the UID and GID numbers must not be changed.

Procedure

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

    To prepare and start multiple instances at once, choose Start of the navigation pathMass Operations Next navigation step Start (including prepare 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. Assign a host to each instance or choose Host Assignment and one of the following options:
    Option Description

    Preferred

    Assign a preferred host that you have set for an instance.

    • If the instance is in status Not running Not Running or Running Running, the currently assigned host is set as the preferred host.

    • If the instance is in status Initial Initial, the host assignment is not applicable.

    • If the preferred host is not available or locked, no host is automatically assigned to the instance.

    Last Used

    Assign the last used host to the instance. If the last used host is not available, SAP Landscape Management assigns the first fit host.

    First Fit

    Assign the first available free host to an instance.

  5. 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.
  6. 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.
  7. Optional: Select the Set Note checkbox and enter a note to be displayed in the Description column of the instance.
  8. Choose Execute.

Results

Prepare
  1. Calls the storage adapter or the virtualization adapter to prepare the IP addresses.
  2. Binds virtual IP addresses and mounts the file systems configured.
    When you prepare an SAP HANA tenant database node:
    • Checks if this node is a potential master host.

    • If the node is a potential master host, prepares the virtual hostnames of all tenants which have virtual hostnames registered on the SAP HANA tenant database node.

    If the potential SAP HANA master node is relocated and there are tenants with virtual hostnames that need to be registered on this master node, they will be bound.

    • For database instances:
      1. If database instances were unprepared using SAP Landscape Management, writes the respective service entries if not present.
      2. Attaches the database to the host. That is, registers the database with the operating system.
      3. If necessary, starts the database listeners.
    • For SAP instances that do not represent a database:
      1. If an SAP instance was unprepared using SAP Landscape Management, writes the respective service entries if not present.
      2. Registers the instance agent with the operating system.
        • For Unix-like systems: Adds the agent to file /usr/sap/sapservices

        • For Windows systems: Adds the agent to the Windows service registry

      3. Starts the instance agent.
    • For custom instances:
      1. Calls operation acc_<custom instance type>_attach.
      2. Performs the necessary actions to register the instance on the host.
  3. The instance status is Not running Not Running.

Start
  1. Starts the instance or the set of instances.

  2. The instance status is Running Running.

Next Steps