SAP HANA 2.0: Welcome to SAP BTP, Neo environment
The second milestone for SAP HANA 2.0 on SAP BTP, Neo environment has been released.
Last year, in September 2020, we outlined our plans and the rationale behind introducing SAP HANA version 2.0 in the SAP BTP, Neo environment. The new HANA version 2.0, is intended to provide a path forward for the upgrade of HANA database systems with version 1.0 on the Neo environment – which will reach End-of-Maintenance (EoM) on June 30th, 2021; it also provides a logical milestone for HANA customers on Neo to eventually migrate to the target state with SAP HANA Cloud.
HANA 2.0 is here!!
With the first milestone release in December 2020, we had announced the availability of SAP HANA version 2.0 on the Neo environment. With this release, you were able to select HANA version 2.0 during ‘new’ database provisioning; using any free quota of SAP HANA entitlements in your Neo environment subaccounts.
Please note that it is recommended to only use HANA version 2.0 for all new database provisioning henceforth so that you do not need an upgrade in the near future.
With the second milestone release in Jan 2021, we are pleased to announce that you will now be able to UPGRADE your existing HANA 1.0 database instances to HANA version 2.0 SP5.
Additional assets on using the recommended tools with HANA 2.0 on Neo will be available in the coming weeks.
I already have running HANA 1.0 database systems. What should I do?
As mentioned, we now have the feature to upgrade HANA 1.0 database systems to HANA 2.0. The specific actions required from you depend on your current HANA system configuration. To check/confirm the configuration of your HANA system, refer the Database System Overview in the Cloud cockpit.
Irrespective of the current HANA configuration, you should ensure that your HANA 1.0 system is ready for an upgrade. To achieve this, you should review that the system meets all the necessary upgrade pre-requisites highlighted in the SAP Note.
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. This upgrade should be as simple as any other HANA version upgrade you have carried out until now.
Of course, it is recommended that you should read through the materials on HANA 2.0 in Neo, to get yourself acquainted with supported/unsupported features and restrictions. You should feel free to reach out in case of any questions.
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.
In the first milestone, we already released the HANA ‘XS’ to ‘MDC’ conversion feature (BETA), as a self-service in the Cloud cockpit. With the second milestone release, this conversion self-service is now in General Availability (GA).
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 your database.
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.
The conversion self-service has been constructed to check your HANA system for the fulfillment of the necessary pre-requisites in order for the conversion to succeed.
The check will report Errors (to be fixed) and Warnings (to be acknowledged and accepted) that need to be addressed before moving forward with a version upgrade. A list of pre-requisite checks and corresponding recommended solutions have been detailed here.
Once the check goes through, the conversion of your XS system to an MDC can start. This can be achieved with the ‘Start Conversion’ action. It is important to note that the conversion does involve a downtime but does not require any rebind.
Once the conversion to MDC is complete, you will be able to verify the System Type change to ‘MDC’ on the overview page. The version upgrade from HANA 1.0 to 2.0 should be as simple as any other HANA version upgrade you have carried out until now.
It is highly recommended to run validations of the conversion and upgrade features on your development/ quality systems, before applying it to your production systems/landscapes. With such a validation exercise, you will be able to document, clarify and apply your learnings during the conversion of your production HANA database systems to MDC and the upgrade to HANA 2.0.
Read through the SAP Notes provided in the blog, check this video showcasing the procedure, and try out the XS to MDC conversion self-service (if required) and the version upgrade from HANA 1.0 to 2.0, on your Dev/QA systems to understand how it works and to foresee any potential issues. In case you face issues, please raise a support incident on the component BC-NEO-PERS-HANA.
Subsequently, you should plan for the conversion and version upgrade for all your HANA systems before June 30, 2021, so that you can enjoy continued support for HANA on the Neo environment. In case the upgrade to HANA 2.0 is not completed by this timeline, you run the risk of running an unsupported HANA version with potentially no bug fixes, security patches, etc provided by SAP.
In case you have further queries on this topic, feel free to contact your SAP Customer Engagement Executive or Account Executive. You can also reach out via our mailbox firstname.lastname@example.org with ‘HANA 2.0 on Neo’ in the email subject for prompt responses.