HANA 2.0 Installation: HDBLCM, Linux OS Prerequisites & Sizing
Comprehensive installation guide for SAP HANA 2.0 using the SAP HANA Database Lifecycle Manager (HDBLCM), covering SAP certified hardware sizing, filesystem mount topologies, Linux OS tuning, user creation, and practical lab caveats.
IntermediateInstallation~20 min studyHANA 2.0 SPS 05 - SPS 07+
Core Learning Objectives
- 1.Master the HDBLCM installation workflow (hdblcm, hdblcmgui, hdblcmweb).
- 2.Understand mandatory Linux OS prerequisites for SUSE SLES for SAP and Red Hat RHEL for SAP.
- 3.Critically evaluate supported enterprise distributions (SLES/RHEL) vs unsupported lab platforms (Rocky Linux / CentOS).
- 4.Configure Linux kernel parameters, swap file buffering, /etc/hosts, and chrony time synchronization.
- 5.Execute pre-installation validation checks and extract SAPCAR archives.
Prerequisites:hana-fundamentals-overviewhana-architecture-services-overview
Definition & Architectural Rationale
Technical Definition:
SAP HANA Database Lifecycle Manager (HDBLCM) is the unified command-line, graphical, and web-based administrative tool used for deploying, configuring, patching, and maintaining SAP HANA database systems and components.
Why this component exists:
Manual compilation and configuration of distributed database binaries, kernel parameters, SSFS security keys, instance profiles, and user authorizations would be error-prone and non-standardized. HDBLCM ensures strict conformance with SAP architectural standards and PAM supportability.
Internal Working & Mechanics
1. Supported Operating Systems vs. Lab Platforms:
- Officially Supported (Production): SUSE Linux Enterprise Server for SAP Applications (SLES 15 SP3/SP4/SP5) and Red Hat Enterprise Linux for SAP Solutions (RHEL 8.4/8.6/8.8, 9.0/9.2). Always verify the SAP Product Availability Matrix (PAM) and SAP Note 2235581.
- Lab / Learning Environments: Administrators frequently deploy experimental lab environments on Rocky Linux 9 or AlmaLinux (RHEL rebuilds). NOTE: Rocky Linux is NOT officially certified or supported by SAP for production HANA deployments. Any lab setup on Rocky Linux must be labeled as experimental for personal study and DBA skill verification.
2. Filesystem Mount Sizing Standards:
- /hana/shared: 1x RAM for single-node (max 1 TB); stores binaries, instance profiles, and trace files.
- /hana/data: 1.2x RAM (minimum recommended by SAP Quick Sizer); formatted with XFS or GPFS.
- /hana/log: 512 GB or 0.5x RAM (whichever is smaller, min 64 GB); formatted with XFS; sub-millisecond latency.
- /usr/sap: Minimum 50 GB.
3. Swap Memory:
While HANA is an in-memory database designed to run in RAM, SAP mandates swap space (typically 2-4 GB minimum or 0.5x RAM for small lab VMs) to prevent OS kernel OOM panics when background processes spike.
4. HDBLCM Installation Workflow:
- Extract SAPCAR archive: SAPCAR -xvf IMDB_SERVER20_*.SAR
- Execute HDBLCM: ./hdblcm --action=install
- Specify: SID (3 alphanumeric, e.g. HDB), Instance Number (00-99), Database Isolation, System Administrator Password, and SystemDB SYSTEM password.
Architecture Flow Diagram
Mermaid DiagramHANA 2.0 Installation: HDBLCM, Linux OS Prerequisites & Sizing
Architectural Flow: The installation workflow proceeds linearly from OS and filesystem prerequisites to SAPCAR extraction, HDBLCM execution, SystemDB instantiation, tenant container creation, and final CLI verification.
Linux Terminal Diagnostics & Operations
Configure and Verify 4GB Linux Swap File for Lab Environment
user: root
Provides OS kernel safety buffer against sudden memory exhaustion during installation and testing.
root@host # sudo fallocate -l 4G /swapfile && sudo chmod 600 /swapfile && sudo mkswap /swapfile && sudo swapon /swapfile && swapon --show
Terminal Standard Output (stdout):
Setting up swapspace version 1, size = 4 GiB (4294963200 bytes) no label, UUID=a48f2190-7d31-482a-9cb2-1110e54d3201 NAME TYPE SIZE USED PRIO /swapfile file 4G 0B -2
Output Analysis: 4GB swap file is mounted with secure permissions (chmod 600) and active on priority -2.
Verify Local Hostname Resolution and IPv4 Binding
user: any
Validates that hostname resolves immediately to local IP without hitting external DNS timeouts.
$ getent ahostsv4 $(hostname -s) && hostname -f
Terminal Standard Output (stdout):
192.168.1.15 STREAM site-secondary 192.168.1.15 DGRAM 192.168.1.15 RAW site-secondary.localdomain
Output Analysis: Local hostname correctly maps to 192.168.1.15 via local /etc/hosts.
Invoke HDBLCM Command-Line Installer
user: root
Launches interactive command-line installation of SAP HANA Database Server and Client.
root@host # ./hdblcm --action=install --components=server,client
Terminal Standard Output (stdout):
SAP HANA Lifecycle Management - SAP HANA Database 2.00.070.00.1679941421 ************************************************************************ Enter Installation Path [/hana/shared]: Enter System ID: HDB Enter Instance Number [00]: 00 Enter Local Host Name [site-secondary]: Do you want to enable secure internal communication (SSL)? [y]: y Enter System Administrator (hdbadm) Password: ******** Enter Database System (SYSTEM) Password: ******** ... Installing SAP HANA Database... Preparing package 'SAP Host Agent'... Installing package 'HDB Server'... Creating SystemDB... Creating Tenant DB 'HDB'... Installation completed successfully.
Troubleshooting & Root Cause Analysis
Production Best Practices & Operational Risks
Mandatory Best Practices
- Always use separate physical filesystems for /hana/data, /hana/log, and /hana/shared in production.
- Never install HANA on general-purpose cloud VM disk volumes with unthrottled burst IOPS; ensure persistent IOPS conform to SAP certification standards.