SAP HANA Installation Steps: A Practical SAP HANA 2.0 Guide

SAP HANA installation is a planned sequence rather than a single command. You prepare the host and operating system, obtain the correct installation media, install the SAP HANA system database, create tenant databases, validate the services, and complete security and administration tasks. This guide focuses on SAP HANA 2.0 on-premise and uses SAP HANA cockpit, SAP HANA database explorer, and the SAP HANA lifecycle management tools.

SAP HANA 2.0 runs as a multitenant system. The installation creates a system database, and application workloads normally run in one or more tenant databases. The system database manages the overall system and can perform system-level administration; a tenant database contains application data and database-specific users.

01Plan the SAP HANA installation

Start with an installation plan that records the system identifier, instance number, host names, installation directories, storage layout, operating-system users, database names, and network requirements. Keep the system identifier within SAP's naming rules and reserve an instance number that does not conflict with another service on the host.

Confirm that the hardware, operating system, file systems, and supported software versions meet the applicable SAP Product Availability Matrix requirements. Use SAP Quick Sizer for workload-based sizing, then validate the result against the certified hardware and storage guidance for the specific SAP HANA release.

The installation design should account for data volumes, log volumes, shared files, backup destinations, and high-availability or disaster-recovery requirements. Separating data, log, and backup storage helps with performance, capacity management, and recovery operations. For a distributed system, document which services run on each host before you begin.

02Prepare the host and installation media

Prepare the operating system according to the SAP HANA installation guide. This includes required packages, kernel settings, time synchronization, name resolution, host connectivity, storage mount points, and authorized operating-system users. The installation user must be able to perform the required actions, while the resulting services run under the appropriate system users such as <sid>adm.

Download installation media from an authorized SAP source and verify its integrity. Place the media in a location accessible to the installation process, or make it available through the supported installation repository. Do not mix component revisions casually: the database software, client packages, and additional components should be selected according to the compatibility requirements for the target system.

Before installation, check that the required ports are available and that firewalls permit communication between the system database, tenant databases, client tools, and administration tools. A failure in name resolution or time synchronization can appear later as a database, host-agent, or service-management problem.

03Install SAP HANA with hdblcm

The SAP HANA lifecycle management tool, hdblcm, supports interactive and automated installation. The graphical installation option is useful when you want guided prompts; command-line execution is useful for repeatable installations and scripted environments. Review every proposed parameter before confirming the installation.

The main installation flow generally includes these stages:

1. Start hdblcm from the SAP HANA installation media.
2. Select the installation action and the components to install.
3. Provide the system identifier, instance number, host information, and installation paths.
4. Define the system database administrator credentials and other requested passwords.
5. Confirm the storage locations and service configuration.
6. Review the summary and begin the installation.
7. Record the installation log and confirm that all selected components completed successfully.

The installation creates the SAP HANA system database and the supporting services. In a distributed deployment, repeat or coordinate the host-related steps according to the selected topology rather than treating every host as an independent database installation.

04Create and configure tenant databases

After the system database is available, create tenant databases for application workloads. A tenant database has its own database users, schemas, objects, and configuration context, while the system database retains system-level responsibilities.

A database administrator can create a tenant with SQL from the system database. For example, the required syntax uses one SYSTEM keyword before USER and one PASSWORD clause:

CREATE DATABASE DB0 SYSTEM USER PASSWORD Manager1;

The executing account requires the DATABASE ADMIN privilege. Use a strong password in a real environment and avoid placing credentials in shell history, scripts, tickets, or source control. After creation, apply the tenant's network, backup, user, and authorization policies before connecting application software.

SAP HANA database explorer is useful for running administrative SQL and inspecting database objects. SAP HANA cockpit provides broader system monitoring and administration across the system database and tenant databases, subject to the privileges assigned to the administrator.

05Validate the installed system

Validation should confirm both service availability and usable database connectivity. Check the system in SAP HANA cockpit, connect with SAP HANA database explorer, and review the installation logs for errors or warnings that require action.

For a local single-host installation, the HDB script is located under /usr/sap/<SID>/HDB<instance number>/HDB. The valid local commands are:

/usr/sap/<SID>/HDB<instance number>/HDB start
/usr/sap/<SID>/HDB<instance number>/HDB stop

Linux is case sensitive, so hdb start is not the same command. HDB acts on the local host only and is not the preferred method for controlling a distributed system. For distributed systems, use sapcontrol with the <sid>adm user:

sapcontrol -nr <instance number> -function StartSystem
sapcontrol -nr <instance number> -function StopSystem

For a broader operational procedure, see SAP HANA start and stop. Confirm that the system database and each tenant database report the expected state after a start or stop operation.

06Check memory and storage after installation

A new system should be checked before application onboarding. Review host-level memory, service memory, data volume capacity, log volume capacity, backup space, and alert status. The host resource view is SYS.M_HOST_RESOURCE_UTILIZATION; useful columns include HOST, USED_PHYSICAL_MEMORY, FREE_PHYSICAL_MEMORY, ALLOCATION_LIMIT, INSTANCE_TOTAL_MEMORY_USED_SIZE, and INSTANCE_TOTAL_MEMORY_ALLOCATED_SIZE.

Service-level memory is available in SYS.M_SERVICE_MEMORY, where the used-memory column is TOTAL_MEMORY_USED_SIZE. For column-store table analysis, use M_CS_TABLES and its MEMORY_SIZE_IN_TOTAL and RECORD_COUNT columns. These checks provide a baseline for later capacity and performance investigations.

For a practical administration workflow, see SAP HANA memory usage. Compare observed usage with the approved sizing and capacity plan rather than changing limits simply because the host appears to have unused memory.

07Complete security and backup configuration

Change temporary or installation-time credentials and create named administrative accounts with only the privileges required for their responsibilities. Apply password, auditing, communication, and authorization policies according to the organization's security standard. Review system-database and tenant-database administration separately because privileges are scoped to the relevant database context.

Configure data volume encryption, log volume encryption, and backup encryption as separate controls. Whenever encryption is configured or changed, back up the root keys and back them up again after any change. If a backup encryption root key is changed and the new key is not backed up, the affected backup can become unrecoverable.

Set up scheduled data backups and log backups, define retention, and test restoration before the system is considered ready. A successful backup job alone does not prove recoverability. Document the backup destination, encryption-key custody, recovery procedure, and responsible operators.

08Finish the post-installation checklist

Complete the following checks before handing the system to application or development teams:

• Confirm the system database and tenant databases are reachable with approved tools.
• Verify that services start correctly after a controlled restart.
• Review SAP HANA cockpit alerts and installation logs.
• Confirm data, log, shared, and backup file systems have appropriate capacity.
• Test administrative access through SAP HANA cockpit and SAP HANA database explorer.
• Create or validate backup schedules and perform a recovery test.
• Record the system identifier, instance number, host layout, tenant names, ownership, and escalation contacts.
• Store root-key backups and operational credentials according to the security policy.

A repeatable installation record is valuable for future system refreshes, troubleshooting, and audit evidence. Keep the approved parameter file, installation logs, topology diagram, and validation results together with the operational documentation.