Upgrades & Lifecycle Management: SPS & Revision Patching via HDBLCM
A step-by-step production runbook for planning, validating, and executing SAP HANA SPS and Revision updates using HDBLCM, pre-requisite backups, OS compatibility checks, and post-upgrade health validation.
Advanced (Senior DBA)Upgrades~20 min studyHANA 2.0 SPS 00 to SPS 07+
Core Learning Objectives
- 1.Decode SAP HANA version, SPS (Support Package Stack), and Revision numbers.
- 2.Execute pre-upgrade compatibility checks against SAP Notes and PAM.
- 3.Perform mandatory full data and log backups prior to commencing patching.
- 4.Execute database binary upgrade using media HDBLCM in CLI mode.
- 5.Conduct post-upgrade verification on catalog consistency, row store, and services.
Prerequisites:hana-installation-hdblcm-prerequisiteshana-backup-pitr-catalog
Definition & Architectural Rationale
Technical Definition:
SAP HANA Lifecycle Management involves applying Support Package Stacks (SPS) and maintenance revisions to update core engine binaries (nameserver, indexserver, client, host agent) using the HDBLCM utility with minimal planned downtime.
Why this component exists:
Database engines require periodic updates to patch security vulnerabilities, resolve engine bugs, and enable compatibility with newer SAP S/4HANA application releases. Executing structured, repeatable upgrade procedures prevents production corruption and rollback panics.
Internal Working & Mechanics
1. Version Nomenclature:
Example: 2.00.075.00.1698204910
- 2.00: SAP HANA Major Version (HANA 2.0).
- 07: Support Package Stack (SPS 07).
- 5: Revision within that SPS (Revision 75).
- .00: Maintenance release patch level.
- 1698204910: Unix epoch compilation timestamp.
2. Pre-Upgrade Validation Checklist:
- Check Operating System compatibility: Review SAP Note 2235581. Ensure SLES/RHEL kernel and GCC libraries support the new target revision.
- SAP Host Agent: Upgrade SAP Host Agent to the latest patch BEFORE upgrading HANA binaries: ./saphostexec -upgrade -archive SAPHOSTAGENT*.SAR.
- Mandatory Backup: Take a verified Complete Data Backup and confirm that all log backups have finished successfully.
- Persistence & Filesystem Capacity: Ensure /hana/shared has at least 30-50 GB of free space to hold the new binaries side-by-side during upgrade.
3. HDBLCM Upgrade Execution:
- Extract media: SAPCAR -xvf IMDB_SERVER20_*.SAR -R /sapmnt/MEDIA/HANA_PATCH
- Launch HDBLCM: cd /sapmnt/MEDIA/HANA_PATCH/SAP_HANA_DATABASE && ./hdblcm --action=update
- Provide SID and passwords.
- HDBLCM performs: Pre-flight checks -> stops database -> updates binaries in /hana/shared/<SID>/exe -> restarts database -> upgrades catalog and SystemDB -> upgrades all tenant databases -> restarts services.
Architecture Flow Diagram
Mermaid DiagramUpgrades & Lifecycle Management: SPS & Revision Patching via HDBLCM
Architectural Flow: Upgrade workflow progresses through pre-flight checks, mandatory data backup, SAPCAR extraction, HDBLCM automated binary swap and catalog migration, concluding with post-upgrade health validation.
Linux Terminal Diagnostics & Operations
Execute HDBLCM Database Update Command
user: root
Executes interactive upgrade of the HANA database engine and client from media directory.
root@host # ./hdblcm --action=update --components=server,client
Terminal Standard Output (stdout):
SAP HANA Lifecycle Management - SAP HANA Database 2.00.075.00 ***************************************************************** Enter System ID: HDB Do you want to continue? (y/n): y Enter System Administrator (hdbadm) Password: ******** Enter Database System (SYSTEM) Password: ******** ... Stopping SAP HANA Database system... Upgrading package 'HDB Server'... Starting SAP HANA Database system... Upgrading SystemDB... Upgrading Tenant 'PRD'... Update of SAP HANA Database components completed successfully.
Troubleshooting & Root Cause Analysis
Production Best Practices & Operational Risks
Mandatory Best Practices
- Always test the exact revision update on a Sandbox or Quality system at least two weeks before applying to Production.
- Never delete old backup files prior to the upgrade; ensure the pre-upgrade full backup and catalog are safely archived.