SAP HANA has always been a vital part of the database portfolio of SAP Cloud Platform since the days of platform inception. But, in 2016, SAP had announced that SAP HANA 1.0 SPS12 will be the final release for HANA version 1.0, and it will have a five-year maintenance term. Consequently, SAP HANA revision 1.0 will reach. End-of-Maintenance in June 2021. This timeline will also have an impact on the SAP HANA version availability in the SAP BTP, Neo environment.
To ensure the business continuity, SAP HANA 2.0 were planned to be made available by Q4 2020 for everyone on the Neo environment.
How to upgrade HANA 1.0 data systems to HANA 2.0?
Are you running a HANA 1.0 Tenant database ‘MDC’ system?
If yes, you should now be able to upgrade your existing HANA system from version 1.0 to 2.0.
Customers running tenant database (“MDC”) systems that are running on SLES 12 SP 5 or RHEL 7.x (RHEL 8.x preferred if you want to go to HANA 2.0 SPS05) can update their SAP HANA 1.0 systems to SAP HANA 2.0 using the Update functionality in the SAP BTP cockpit.
Are you running a HANA 1.0 single-container ‘XS’ system?
As you may already be aware, HANA systems being in an ‘MDC’ i.e., Multi-tenant Database Container configuration is a pre-requisite for migration to SAP HANA version 2.0.
SAP already released the HANA ‘XS’ to ‘MDC’ conversion feature, as a self-service in the Cloud cockpit.
The service can be used to convert existing HANA XS systems to HANA MDC systems.
As the diagram above indicates, the XS system will be converted into a ‘Tenant’ database of the new MDC system with the same name. There should not be any change to the SID alias of the database.
Customers running single-container (“XS”) systems can convert their systems into MDC systems. After the conversion, they will be able to update their SAP HANA 1.0 systems to 2.0 using the Update functionality in the SAP BTP cockpit.
During the conversion, you will also be asked to set a password for the SYSTEM user of the newly created tenant database. The old database user of your XS system should continue to be available in the new tenant database.
Few prerequisites in the move from HANA 1.0 to 2.0:
- The version of your current SAP HANA database system must be at least 1.00.122.29 or higher (ideally latest).
- SAP HANA 1.0 systems should be running on OS SLES12 SP5 or higher or RHEL 7.x or higher to be available for conversion and upgrade to HANA 2.0.
- SAP HANA 2.0 in the Neo environment will only support SAP HANA tenant database systems (MDC – Multitenant Database Containers).
- SAP HANA 2.0 in the Neo environment will only support the SAP HANA extended application Services, Classic model (XSC). SAP HANA extended application services; advanced model (XSA) will not be available.
Important Restrictions for SAP HANA 2.0 in the Neo Environment:
- For the installation of new database systems, SAP HANA 2.0 in the Neo environment only supports database systems sizes of 64GB and upwards.
- SAP HANA 2.0 in the Neo environment only supports SAP HANA tenant database systems (MDC). SAP HANA single-container (XS) systems will not be supported anymore.
- SAP HANA 2.0 in the Neo environment will only support SAP HANA extended application services, the classic model (XSC). SAP HANA extended application services; advanced model (XSA) will not be available.
- Tool restrictions:
- SAP Web IDE for SAP HANA and SAP HANA XS Administration Tool will be supported.
- SAP HANA cockpit 1.0 will not be supported.
- On-premises installations of SAP HANA studio and SAP HANA cockpit 2.0 can be connected via database tunnels.
Important Differences between SAP HANA 1.0 and SAP HANA 2.0:
- Upgrading from SAP HANA 1.0 to SAP HANA 2.0 is a major version change and your applications may be impacted by the upgrade. We recommend that customers and partners thoroughly test their applications or solutions after the upgrade.
- Several features and capabilities have been removed in SAP HANA 2.0.
- The key feature of benefit to customers is the MDC. Although it was introduced in HANA 1.0, they can logically separate schemas into logically independent data containers. That implies that backups/ restores (used in the context of system refreshes) can be done separately. An added advantage, we have seen customers taking is landscape simplification through having non-prod systems in one SAP HANA 2.0 MDC and production in another. This saves on costs of licenses and maintenance or upkeep and has the potential to save on hardware costs yet logically partitioned.
- One other key feature in HANA 2.0 is the XSA, which allows using HANA as a true platform for end-to-end software development into full-fledged applications.
P.S. For More Information Visit www.v3it.com
References:
- launchpad.support.sap.com. (n.d.). https://launchpad.support.sap.com/#/notes/2946614
- Baburao, M. (2021, February 17). SAP HANA 2.0: Welcome to SAP BTP, Neo environment. SAP Blogs. https://blogs.sap.com/2020/12/22/sap-hana-2.0-welcome-to-sap-cloud-platform-neo-environment/
- Baburao, M. (2021, February 16). HANA 2.0: Coming soon to SAP BTP, Neo environment! SAP Blogs. https://blogs.sap.com/2020/09/01/hana-2.0-coming-soon-to-sap-cloud-platform-neo-environment/