Skip to Content
Technical Articles

SAP HANA revision upgrade step-by-step


Introduction. Basis Administration in the Age of SAP HANA requires new skills from SAP Basis Administrators. One of them HANA DB Maintenance & Upgrade. For example, DB-revisions should be installed at regular intervals to avoid errors and to keep your Database up to date


Prerequisites for HANA DB Upgrade.

You want install a new revision on SAP HANA database. For example, in EWA report you found “A critical SAP Note exists for your current SAP HANA revision”


Corrections are shipped in the form of Revisions and Support Packages Stack (SPS) of the product’s components. This blog post about Revisions.

Find correction on SAP Launchpad. For example, if you want upgrade Revision Rev037_1 to Rev037_3


Don’t forget about installed plugins. Check installed Plug-ins in Hana Studio or in DBACockpit transaction.
Download SAR archives with a correct version from Launchpad too
NB: For HANA DB Rev037_3  ->LCAPPS plugin must be 037.03 version too
Let’s start update process in Dev landscape.
Extract files from SAR archives.
NB: Very important moment. Structure after extracting procedure must be separated
Stop SAP systems. Dialog Instance (-es) – ASCS(SCS) – ERS
NB: stopsap j2ee  *for Java systems
       stopsap R3 *for ABAP systems
Make backup for SYSTEMDB and ALL tenants
NB: su <sidadm>
/usr/sap/<sid>/<sid><instance>/HDB stop
NB: Average time for HANA DB stopping: 5-20 minutes (this measure depends on the DB-size).
Now we are ready for an upgrade
Run command from root privileges from a folder with extracted  HANA Revision files,
NB:For example OS-path may be:
/<path>/SAP_HANA_DATABASE/hdblcm –ignore=check_signature_file
NB: Installation process must be from SYSTEM (SAP HANA initial  DB super user)
If you lock this user for security reasons ->
Unblock SYSTEM user for this task
Updating process…
Updating process (continuous)
Check Hana NEW version after updating the procedure.
NB: /usr/sap/<sid>/<sid><instance>/HDB version
HANA DB already started automatically at this point so time to start application server in reserve sequence
ERS – ASCS (SCS) – Dialog Instance(es).
NB: startsap j2ee  *for Java systems
       startsap R3 *for ABAP systems
Log-in in your SAP system to 000 client and check output of transaction SICK
NB:Result must be  – no errors reported.
Repeat steps above for HANA DB in QAS system and after additional approvals in  PROD landscape.


SAP BASIS Routine task with examples from real life was provided

Related Notes / Guides:


SAP HANA Administration Guide 2.0 SPS 03

SAP Note 1948334 – SAP HANA Database Update Paths for SAP HANA Maintenance Revisions

2378962 – SAP HANA 2.0 Revision and Maintenance Strategy 


You must be Logged on to comment or reply to a post.
  • Correction  about this statement:

    NB: Installation process must be from SYSTEM (SAP HANA initial  DB super user)
    If you lock this user for security reasons ->
    Unblock SYSTEM user for this task

    I am rechecked SAP HANA Administration Guide.

    "The SYSTEM user is not required to update the SAP HANA database system;
    a lesser-privileged user can be created for this purpose."

    • Hello, Iurii,

      Backup procedure mandatory

      Look at my separate blog-post -

      You can also backup and the whole server too

      My friendly advice look at Relax-and-Recover(ReaR) utility for this purpose.

      Thank you!