Developer Center HOWTO - Update your SAP HANA, developer edition on AWS
The upgrade process here is only for HANA release 68.
At this time, there is no upgrade process to release 70 (or later releases). In order to move to these releases, you will need to migrate your data and code to a new virtual instance.
For questions about this process, please visit the Q&A forums.
[2014-01-02] Updated guide to show upgrade to HANA Revision 68
[2013-08-20] Updated guide to show upgrade to HANA Revision 60
[2013-06-06] Updated a few section based on Mani's recommendations below in the discussion - thanks, Mani!
[2013-06-06] Removed "do not upgrade" alert, added 0 - Pre-Requisites
[2013-06-06] Added "do not upgrade" alert
[2013-06-05] Updated guide to show upgrade to HANA Revision 56[2013-02-21] Updated guide to show upgrade to HANA Revision 48
[2013-02-21] Added statement about other cloud infrastructure providers (CloudShare, PT, KT)
This document describes how to update your SAP HANA, developer edition on Amazon Web Services (AWS) to a later revision. This guide only works with SAP HANA, developer edition on AWS, not with other cloud providers. For CloudShare, KT and PT, please contact us on firstname.lastname@example.org and we will help you with the update. [Note: For SPS6, if you want to use the Predictive Analytics Library or XS Engine, we recommend to go with instance sizes >>16GB]
If you still have HANA version 1.00.28, 1.00.35, 1.00.48, 1.00.56 or 1.00.60 on your AWS images, the following will guide you to update to 1.00.68 (SPS6).
[Note: A HANA DB version of at least 1.00.35 is a per-requisite for the installation of a license key (see Developer Center HOWTO - Get and Install a SAP HANA, developer edition License File) that you need to request within 90 days of running your instance]
You can read the step-by-step guide below, or watch and follow along this 4 minute video tutorial (this shows the procedure to upgrade from Revision 28 or Revision 35, but the only difference to an upgrade to Revision 60 is that you have to call update.sh instead of hdbupd):
Step 1 - Create a EBS Volume with the update installer
We have created a Elastic Block Store (EBS) Snapshot with the update installer that we have shared with all registered HANA@AWS users. The Snapshot Id's for the various regions are:
|AWS Region||Snapshot Id|
To create a new volume from the snapshot (see screen shot):
- Navigate to the AWS Console on [logon with the AWS account you used to create your HANA instance]
- Choose EC2
- Make sure you are working in the Region you created your HANA instance in (dropdown in top right corner)
- Pick INSTANCES > Instances from the Navigation panel
- Select your HANA instance and look for the Zone property on the Description tab. Remember the value for Zone, as you will need it later
- Pick ELASTIC BLOCK STORAGE > Snapshots from the Navigation panel
- Change the Viewing filter dropdown to Private Snapshots - you should see a 5 GB snapshot in the list, with one of the Snapshot Id's listed above (depending on your region). The description of the snapshot should be "SAP HANA Developer Edition Rev 60"
- Right-click the snapshot and pick Create Volume from Snapshot from the context menu. Or select the snapshot and click the Create Volume button, whatever you prefer
- On the popup, choose Standard as Volume Type, enter 5 GiB as Size and pick the Zone value you found on your HANA instance from the Availability Zone dropdown
- Click the Yes, Create button
=> You have created a new EBS volume with the update installer.
Step 2 - Attach the newly created EBS volume to your HANA instance
Next, you will have to attach the volume you created in Step 1 to your HANA instance:
- Pick ELASTIC BLOCK STORAGE > Volumes from the Navigation panel
- In the list of volumes, you should see your newly created 5 GB volume in State "available"
- Note down the Volume ID - you need it in step 6 for detaching it
- Right-click the volume and pick Attach Volume from the context menu. Or select the volume and pick Attach Volume from the More... menu button, whatever you prefer
- From the Instances dropdown, pick your HANA instance
[Note: if you don't see your HANA instance in the dropdown, check that the Availability Zone of your volume is the same as the one of your instance. If it's not, delete the volume and go back to Step 1]
- Remember the value shown for Device on the popup, as you will need it later
- Click the Yes, Attach button - the State column for your volume should change to "in use"
=> You have attached the EBS volume with the HANA update installer to your HANA instance.
Step 3 - Mount the device
OK, here's some Linux stuff - you now need to "mount" the device associated with your volume into the file system of your HANA instance. This will allow you to switch to a directory in the file system and see the content of the volume. So mount the device:
- Start your instance if it's not already started
- Use an SSH client (e.g. putty) to logon to the OS of your AWS instance as user root. [Note: if you don't remember how to logon to the OS, check http://docs.aws.amazon.com/gettingstarted/latest/wah-linux/getting-started-deploy-app-connect.html]
- Create a new directory (e.g. /sap/update, but choose whatever you want) by executing
- Mount the device that is associated with the volume you created (the value for Device that you remember from Step 2, it will look somewhat like /dev/sdf) to the directory you just created by executing
mount /dev/sdf /sap/update
[Note: use your values for device and directory when executing the mount device directory command]
- Check the content of your update directory (you should see a file update.sh along with some sub-directories) by executing
[Note: use your value for directory when executing the ls directory command]
=> You have everything in place to start the update process
Step 4 - Update your HANA DB
So far it was all preparation - now let's run the update:
- Navigate into the update directory you created by executing
[Note: use your value for directory when executing the cd directory command]
- start the update installer by executing
- When prompted, choose your HANA DB with SID HDB by typing 0
- When prompted, enter the password of user hdbadm - if you ignored our advice and never changed the password of that user, it is HANAabcd1234.
[Note: if you ignored our advice and never changed the password for hdbadm, now might be a good time to change it. Exit the update installer, execute passwd hdbadm, enter and confirm the new password and start the update installer again]
- When prompted, enter the password of database user SYSTEM - if you ignored our advice and never changed the password of that user, it is manager.
[Note: if you ignored our advice and never changed the password for SYSTEM, bla bla, yadda yadda yadda...]
- The update will run for a couple of minutes and as a last step will stop and start the HANA DB, install the additional package HANA_AFL (the application functions library you need to call those built-in statistical functions)
- Check the version of your HANA DB, either by double-clicking the connection in HANA Studio or from the Linux command line (you will need to become user hdbadm) by executing:
su - hdbadm
=> Congratulations! You have now updated your HANA DB on AWS to version 1.00.68
Step 5 - Get the Client Software
HANA Client and HANA Studio for Linux and Windows, as well as the SAPUI5 plugin for HANA Studio are available in directory /sap/update/media on your HANA Server machine as long as the update volume is mounted. Use a scp (e.g. WinSCP is great for Windows users) or sftp client to download the zip files, or copy everything into directory /media on you HANA server.
The tools are also available for download from the Developer Center.
Step 6 - Clean up
Done? Not quite. You have created an EBS volume that you don't need any more, and AWS will charge you for that volume. Although it's not going to be a lot of money, it seems like a good idea to delete the volume. To delete the volume:
- In your SSH session, navigate out of the update directory and back into the root users home directory by executing
- Unmount the device by executing
- This was the last command you need to execute in your SSH session, so you can end the session by executing
- Go back to your AWS Console on https://console.aws.amazon.com
- Pick ELASTIC BLOCK STORE > Volumes from the Navigation panel
- Find the right volume by the Volume ID you wrote down in step 2, right-click the volume and pick Detach Volume or Force Detach from the context menu. Or select the volume and pick Detach Volume or Force Detach from the More... menu button, whatever you prefer.
- On the popup, click the Yes, Detach (or Yes, Force) button. The State column of the volume should now change to "available"
[Note: you might have to press the Refresh button to see the State column change]
- Right-click the volume and pick Delete Volume from the context menu. Or select the volume and pick Delete Volume from the More... menu button, whatever you prefer.
=> Now you're really, really done
In case of trouble...
We tested the update procedure extensively, and never experienced issues. However, we're dealing with software here, so things can go wrong
Please let us know on the forum about any issues with the update. Some typical sources for trouble:
- You don't see the snapshot with the update. Please contact email@example.com
- You cannot attach the volume to your HANA instance. Check that the availability zones for instance and volume are identical
- You cannot logon to you HANA instance via SSH as it keeps asking for the root password. You need to pass your AWS key pair to SSH client as explained in Get your own SAP HANA, developer edition on Amazon Web Services (Part 5). If you don't have the *.pem file, you are screwed. In that case your only option is to create key pair, download the *.pem file and create a fresh instance (as described in the pre-requisites section of the above-mentioned document)
- The update fails or the DB doesn't start up after the update. Try to manually stop and start the DB (run ./HDB stop then ./HDB start as hdbadm) and check in HANA Studio if it comes up green within a few minutes. If it doesn't, have a look into the update log file (the path is shown at the end of the update) to find any clues. Also check the server logs (from the Studio by double-clicking the connection - you will have to enter the hdbadm credentials). If you cannot get the updated HANA DB started, send us the logs to firstname.lastname@example.org
I hope you won't need any of these options and everything works smoothly. If you have any suggestions on how this HOWTO document can be improved, please leave a comment below.
Have fun with your HANA developer instance!