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.
-
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
Results
- Calls the storage adapter or the virtualization adapter to prepare the IP addresses.
- 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:
- If database instances were unprepared using SAP Landscape Management, writes the respective service entries if not present.
- Attaches the database to the host. That is, registers the database with the operating system.
- If necessary, starts the database listeners.
- For SAP instances that do not represent a database:
- If an SAP instance was unprepared using SAP Landscape Management, writes the respective service entries if not present.
- 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
-
- Starts the instance agent.
- For custom instances:
- Calls operation acc_<custom instance type>_attach.
- Performs the necessary actions to register the instance on the host.
- For database instances:
-
The instance status is Not Running.
-
Starts the instance or the set of instances.
-
The instance status is Running.
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.