SAP HANA 2.0 Database Upgrade – How to Guide
With the release of HANA 2.0 SPS 02 database and the fact that HANA 2.0 is mandatory for S/4HANA 1709 release, many customers who are embarking on S/4HANA journey will be faced with the task of upgrading their current HANA 1.0 database to HANA2.0.
For HANA 2.0, there are minimum operating system and hardware requirements that needs to be fulfilled. These changes may require a OS and/or Hardware upgrades based on your current infrastructure. Recently, I had to recommend Hardware and OS upgrades to a customer, who was running their HANA 1.0 DB on an Intel Ivy Bridge based hardware and old OS version. They were planning to upgrade S/4HANA 1610 to S/4HANA 1709 which required HANA 2.0. These upgrades, if necessary, will add additional time to the overall project and it’s recommended to plan so that minimum requirements can be completed in time before the actual database upgrade. Also with HANA 2.0, Multitenant Database Containers (MDC) are mandatory staring with HANA 2.0 SPS01. So, when upgrading to HANA 2.0 SPS01 or higher, if your HANA 1.0 is a single-DB system, then the upgrade will automatically migrate the single-DB to MDC.
Below, I have detailed the steps to perform HANA 2.0 upgrade and other relevant SAP notes and release information.
High level steps include:
- Download SAP HANA 2.0 Platform Edition Software
- Check Hardware and Operating system requirements
- Backup database
- Update the SAP Host Agent
- Run hdblcm
- Check upgrade logs
- Update LCAPPS
- Update HANA DB Client
- Backup database
Relevant Documentation and SAP Notes:
Product Availability Matrix (PAM): SAP HANA Platform Edition 2.0
SAP HANA 2.0 – What’s New : HANA 2.0
SAP HANA Server Installation and Update Guide: Installation and Upgrade Guide
Important Release Notes: Release Notes
Note 2423367 – Multitenant database containers will become the standard and only op. mode
Note 2399995 – Hardware requirement for SAP HANA 2.0
Note 2055470 – HANA on POWER Planning and Installation Specific Central Note
Note 2380257 – SAP HANA Platform 2.0 SP00 Release Notes
SAP HANA 2.0 Upgrade Procedure:
HDB = SAP HANA Database
Please click here to download the HANA 2.0 DB upgrade document in pdf format. Hope this blog is helpful for the SAP community. If you have any questions or comments, please let us know in the comments section.
Thank you.
S/4HANA RIG
Hi Venkata,
thanks for the details, but I think some steps are missing for a successful upgrade:
I think this steps should be added to cover the complete scope of steps for an upgrade.
Regards,
Jens
Hi
Thanks, i upgraded my HANA DB from 1.0 SP12 to HANA 2.0 SP3.
I have one question regarding the LCAPPS, can you tell me which is the LCAPPS version i have to download and Install
Regards,
Sebastian
Hi Sebastian,
How long does it take the migration process in average?
Regards,
Slavisa
It again depends on the Tenants. Roughly it takes less than one and half hours for 5 tenants.
We are running HANA 1.0 SPS 12 on ivy bridge. We want to upgrade to HANA 2.0 as HANA 1 support will be ending next next year.
What due diligence can we do to determine whether we can upgrade to HANA 2.0 on the existing hardware ?
Is there a big enough HANA customer base using HANA 2.0 on ivy bridge ?
Thanks
Atul Walia
Ivy Bridge is no longer supported for Hana 2.0 Production. You will need Hasswell or above. You can still deploy Sandbox/Dev on Ivy Bridge but don't expect any performance out of it. Go through Hana Hardware requirements here: https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/appliances.html
Also look at this:
Hardware Requirements for SAP HANA 2.0 on Intel-Based Hardware Platforms
Starting with SAP HANA 2.0 computing nodes with at least Intel Haswell CPU or later are strongly recommended. However, SAP's requirement remains Intel Westmere CPU. Specifically, if you are running an upgrade of a productive HANA system from SAP HANA 1.0 to SAP HANA 2.0 you can use Intel Ivy Bridge or Westmere CPU based compute nodes. To evaluate an eventual performance impact please refer to www.sap.com/benchmark.
For the latest SAP Notes and documentation, see