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.
Please note that it is highly recommended to take note of important restrictions and SAP HANA Tools support for SAP HANA version 2.0 in the Neo environment before you start working with it.
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 email@example.com with ‘HANA 2.0 on Neo’ in the email subject for prompt responses.
thanks for the information, we are looking forward to the migration to HANA 2.0 for our databases.
We currently cannot find any information on which tools will be available for transport management. Currently, we use transport requests within HANA application lifecycle management for promoting our database and XSJS changes into test and production databases. Is this still the way to go for HANA 2.0 in Neo? Or is the solution something similar to the MTA deployment process?
Sorry for the delay in my response.
You should be able to use the same HANA ALM transport tools with HANA 2.0 on Neo as well.
Kindly try it out after the upgrade and let me know in case of any issues.
Thanks and regards,
We have available the option to upgrade our MDC database to HANA 2.0. Should any additional action be taken to convert our XSC developments to XSA or is this transformation performed automatically by the upgrade process?
The upgrade path for HANA 1.0 to HANA 2.0 will be available soon. As you may have seen from my previous blog, HANA 2.0 on Neo will still only support XSC and not XSA. So this conversion will not be required for the HANA 2.0 upgrade.
Thanks and regards,
Thanks Manjunath, we are going to proceed with the update as it does not require service conversion.
Hi! Normally is a pre restart the database necessay. Is here not the case?
Thanks and regards
Both the MDC conversion and version upgrade activities involve downtime. No special/additional restart is required.
I have an XSC database with size 32 GB. Will an upsize to 64 GB be required before I can upgrade to HANA 2.0?
No. We support HANA 2.0 upgrades for 32GB HANA databases as well. But, during MDC conversion if the pre-requisite check indicates that an upsize is necessary then it may be necessary. An upsize to 64GB is not a general rule for HANA 2.0 upgrades.
Hope this helps.
Thanks and regards,
Hello, we're running our DB on XS 32GB, the update check indicates: 'SAP HANA XS systems of size 32GB or lower can be converted to MDC only after OS migration to SLES 12 SP 5.' So, in my understanding we need to update our OS first (to do the HANA 2.0 upgrade with a 32 GB system). How to do an OS upgrade? Do we need to open a service request (as mentioned here: https://launchpad.support.sap.com/#/notes/3033218) ? Any help would be appreciated.
Indeed, the four steps that you would need to upgrade your 32GB HANA XS system to HANA 2.0 are as follows:
As for the OS upgrade, the process would require system preparation from SAP before you can trigger the OS upgrade. The action required from your end would be a simple database system restart.
We are currently in the process of preparing systems for the OS upgrade and reaching out to customers in waves. In case you have not received any such communication and you are ready to move ahead with the OS upgrade, please feel free to raise a support incident and we will work with you on your OS system preparation on priority. The procedure and component can be found in the SAP Note: https://launchpad.support.sap.com/#/notes/2946614 (refer section 'Migrating to SLES 12 SP 5').
Hope this helps.
Thanks and regards,
Perfect, that helps. Thank you.
In all ours HANA DB's we received following message after checking the migration (xs -> mdc) requirements:
Some of the database users in this system are authenticated through the SAML identity provider SAP ID Service. After the conversion, this authentication method will no longer be supported. In addition, the database users might be locked out and won't be able to connect to the converted system. To proceed with the conversion, view the details of this check to see the affected database users in this system and enable another authentication method for the database users.
How to enable another authentication method for the database users?
Just to clarify, SAML as an authentication method will continue to be supported for HANA MDC.
It will also be possible to configure SAML authentication against any IDP (external or SAP-internal like SAP ID). The difference with HANA MDC is that there is no longer a default configuration for SAP ID.
But post-conversion, you are free to set up SAML authentication in tenant databases on your own.
Hope this helps.
Thanks and regards,
Thank you for your prompt reply!
The question is how to enable another authentication method ? As I'm not from operation rather a developer. Do I need to create a ticket?
Planning to migrate from HANA Cloud (on Neo) to HANA Cloud (on Foundry).
Is it mandatory to also migrate SAC on Neo to SAC on Cloud Foundry ?
Is the effort the same, in the sense that if the DB is migrated, SAC's platform will automatically changed from Neo to CF, or is the effort separate to migrate SAC from Neo to Cloud ?
Unfortunately, I am not completely well versed with the SAC environment specifics.
I would recommend reaching out to any SAC team contact. Sorry for that.
one of our client is upgrading their Neo 1.0 to 2.0. We prepared most of the pre-requisite for it and basis team has upgraded the system with the help of SAP.
This is the current version after the upgrade, one thing I noticed that we have a procedure which is executing some statements and that procedure is been called in xsjobs through xsjs, Some how scheduler trigger the procedure statement as some partial statements under the procedure is getting execute but not the complete statement is executing.
JOB Schedular dashboard is showing below error.
Rep task in as we can see the data in stage table which is target table of rep task, and then simply we are fetching records from stage table and inserting in Final Target table.
Once insertion is completed then we are truncating the data from stage table.
However, I can see the data in stage table and no data inserted in target table. Somehow, partial statements is executing but not the whole statement is.
If I execute the rep task or the procedure manually then it is getting successful and all the statements inside the procedure is executing successfully.
This is something we are facing at this time, Do we need to check any setting parameters or there could be some other issue for it?
Please guide me. We need to resolve it asap then we'll upgrade the PROD instance.
For this issue, I would strongly recommend opening a support ticket/incident on the component BC-NEO-PERS-HANA, so that the relevant experts can take a look at the same.
I don't think the blog would be the right channel to communicate/interact.
Thanks for your understanding.