SAP HANA 2.0 SPS 05 Installation and Update | Hands-on
With this blog series we provide an update with the latest information about SAP HANA 2.0 SPS 05.
For the overview post, see What’s New in SAP HANA 2.0 SPS 05.
For a more general discussion on the topic, see
Any good? Post a comment, share on social media, and/or give a like. Thanks!
What’s New – Installation and Update
SAP HANA Platform
We can be brief about what’s new for the installation and update topic area for the latest SAP HANA 2.0 SPS 05 release.
- NEW: We can enable data and log volume encryption at installation time.
- CHANGED: We can now use the local secure store (LSS) for production. LSS was introduced last year with SPS 04.
As described in the What’s New in SAP HANA 2.0 SPS 05 overview blog, when compared, we can safely put the Installation and Update topic area in bimodal IT camp number one: predictable. In fact, we have to back to 2014 for the last major innovations in this domain. Changes at the time were coming so fast, we wrote a blog about it
Since, it has been an extra parameter here, a minor enhancement there.
- SPS 04: support for persistent memory and install_execution_mode parameter
- SPS 03: software authentication verification and database selection for XS advanced
- SPS 02: AFL update without restart
- SPS 01: installation defaults to tenant database mode
Good thing or bad? Very good would be my vote. You want operations to be predictable. The installation process for SAP HANA has been consistent for the last 6 years and with SPS 05 will remain the same for another five.
If you are new to this topic, we can recommend the video tutorial series and blog posts created for the SPS 02 release (2018), we cover the topic in much detail for every component: server, client, studio, XS advanced, etc. As very little has changed, this information is still accurate.
SAP HANA Cockpit
Although there are a lot of new features introduced with SAP HANA 2.0 cockpit SP 12, concerning installation and update we can be short: it is the same as before, no new features.
The installation uses the same HDBLCM tool as for the database server and other components with a slight modification: we call the tool using a script (hdblcm.sh) instead of directly (hdblcm) to pass some parameters along. To automate (batch), we can use the same process as with the database. This is illustrated below in this blog.
Since the first release of SAP HANA cockpit 2.0 with SAP HANA 2.0 SPS 00 in 2016 only once was there an entry for the Installation and Update topic with SP07: support for installation into existing databases.
SAP HANA 2.0 SPS 05 – Installation and Update
Short tutorial video showing selections choices and procedure (server only).
SAP HANA Cockpit 2.0 SP 12 – Installation and Update
Short tutorial video showing selections choices and procedure.
SAP HANA Cockpit
Always check the documentation and release notes before starting the installation. This might save you a lot of time later on.
Hardware and software requirements are documented in the SAP HANA Cockpit Installation and Update Guide, that is to say, the reference to the actual SAP Note/KBA where this is recorded.
Although you can add SAP HANA cockpit to an existing SAP HANA system, in the standard architecture it contains an SAP HANA, express edition database (persistence), the XS Advanced runtime, plus several Node.js applications, including
- SAP HANA cockpit – system administration tool
- SAP HANA cockpit manager – metadata management tool
- SAP HANA database explorer – catalog browser and SQL console
- SAP HANA SQL Analyzer – execution plan analysis
From the cockpit we make named database user (e.g. SYSTEM) connections to SAP HANA systems (release 1.0 SPS 12 or later). In addition, for connections to the system database to start/stop. offline troubleshooting, or recover we can also add an operating system account, typically the <sid>adm user.
You can download SAP HANA cockpit 2.0 from Software Downloads on the SAP ONE Support Launchpad. Time of writing, SP12 was the latest version but typically you always install the latest version.
The SAR file starts to approach the 4 GB. If your network connection is good enough, you might get away with downloading the file directly (click the link) otherwise check the box and select the shopping cart. Click Download Basket on the bottom menu bar to verify.
Download Manager and File Transfer
To download multiple or larger files unattended, get the Download Manager (also from Software Downloads).
Unzip the ZIP and put the JAR where you like or leave it where it is). Should you have a properly configured Java environment, double clicking the JAR will execute it. Otherwise, run command
java -classpath "DLManager.jar" dlmanager.Application
If you need a JVM, go to
Next, you need to transfer the file to the host. You can use secure FTP clients like WinSCP or in case this concerns a cloud-hosted environment use a cloud shell command. For Google Cloud Platform, for example, use
gcloud compute scp SAPHANACOCKPIT12_14-70002299.SAR hanacockpit:/install
To extract, you need to download SAPCAR from Software Downloads. Should you recycle the server, check if the SAP host agent is still present and run SAPCAR from there.
/usr/sap/hostctrl/exe/SAPCAR -manifest SIGNATURE.SMF -xvf SAPHANACOCKPIT12_14-70002299.SAR
Like the database, we install SAP HANA cockpit with the SAP HANA Database Lifecycle Manager (HDBLCM) except this time via a shell script and not directly
We are prompted to enter
- installation path
- local host name
- system identifier
- instance number
- master password
Default values are provided including Password1 as master password (joke, that’s a joke – you need to come up with one yourself and better make a strong one as it will be the password for all superusers
- <sid>adm – OS
- SYSTEM – system database
- SYSTEM – cockpit tenant database
- COCKPIT_ADMIN – XS advanced
Default SID is H4C and instance number 96. These are arbitrary values and can be changed as desired. Note that by default port-based routing is used and that the instance number is present in a number of TCP ports, e.g. 3<instance_number>30 for the XS controller, etc., which may affect the firewall configuration. Port numbers (range) are configurable.
As mentioned, cockpit uses the same installer as the database so should you want to perform an unattended installation with customised settings, see the platform documentation
- Parameter Reference, SAP HANA Server Installation and Update Guide
Summary before execution shows XS Advanced administration user: COCKPIT_ADMIN and the XS advanced org and space (SAP, HANACockpit). Also note that the default domain might be different from the value expected. We can change easily after the installation.
- 2245631 – Routing Mode and Default Domain configuration for SAP HANA extended application services, advanced model
Note the built-in database is SPS 04 and the location of the log files (should anything go wrong). The installation takes about 45 minutes.
When all is well, the installation ends with
SAP HANA Cockpit System installed
Launch SAP HANA cockpit by opening https://<hostname>:51026
Launch SAP HANA cockpit manager by opening https://<hostname>:51028
When we access the cockpit URL, the browser returns an invalid certificate warning and we cannot connect. SAP HANA cockpit use self-signed certificates and this is like printing your own passport. It does not get you very far.
For test, demo, and training, you can add the certificate to Keychain (macOS) and mark as trusted or install the certificate as root (Windows). For anything serious, get proper certificates. Ask the network admin if that is not you. See the blog post for some suggestions
Reload the page and we should get routed to the XS Advanced user authentication and authorization (UAA) service. This is a different port, so in case you only opened up 51026 and 51028 through the firewall you may get stuck at this point and need to go back to the network admin.
If not, we get an error message (with the promised land in sight, how painful!). Fortunately, we are informed what to do: ask ourselves to launch the cockpit manager tool.
We are making progress. We are connect to the cockpit manager although no databases are registered yet. There are no groups and there is one user (cockpit admin).
From the bottom bar, we can now navigate to the cockpit (opens in new tab). There is nothing to do yet but we can navigate back to Manage Cockpit (opens in another tab). Let’s add a database.
As with cockpit, always check the documentation and release notes before starting the installation.
- SAP HANA Platform
- 2844322 – SAP HANA Platform 2.0 SPS 05 Release Note
- 2235581 – SAP HANA: Supported Operating Systems
Supported operating system requirements have not changed and are the same as for the latest revisions of SPS 04 (e.g. SLES 12 SP05 or 15 SP1).
As with cockpit, download the full SAP HANA platform SPS (14 GB) from Software Downloads.
Click Download Basket on the bottom menu bar to validate your choice before downloading.
In case you only need the server component (or a new revision), go to Support Packages and Patches. IMDB_SERVER is 3.5 GB. Make sure to select LINUX ON x86_64 in the header.
Download Manager and File Transfer
Use Download Manager and file transfer to copy the file to the hana host. There are many ways to do this. For cloud-based systems, use the command line secure copy (scp) command. Alternatively, store this file in cheap cloud storage or on a drive that you attach to the image.
gcloud compute scp 51054084.ZIP hana-vm1:/install
The SPS comes as ZIP file, the component revisions as SAR. Use unzip or SAPCAR to extract.
The first level contains label information for automation. The second level all components.
For SUSE Linux Enterprise Server (SLES), use YaST to configure host and network settings.
Yast > Network Settings > Hostnames configures /etc/hosts
Yast > System > Network Setting: configures /etc/resolv.conf
For new systems, preparing the environment should be planned and executed carefully. For this hands-on, I used an existing SAP HANA, express edition system and removed the existing installation.
Go down the path to the server and run the SAP HANA database lifecycle manager (HDBLCM):
cd DATA_UNITS/HDB_SERVER_LINUX_X86_64 ./hdblcm
Note that besides the server, the client is detected, the application function library (AFL), EML, EPM-MDS, smart data access (SDA), the local secure store (LSS), XS advanced runtime. and different applications from XSA_CONTENT, including the SAP Web IDE and the database explorer.
For a database-only installation, we are prompted to enter
- installation path
- local host name
- single or multiple host (i.e. distributed) – adding a second host automatically makes it scale out
- system identifier – no default value
- instance number
- worker group – standby or extension node are alternatives (exceptional cases)
- system usage
- enable encryption – SPS 05 alert! New Feature
- location of data and log volume
- restrict memory allocation – e.g. to the licensed amount
- certificate host name – for SSL connections
- passwords for <sid>adm and SYSTEM
- OS user login shell, ID, and home
- reboot – cryptical description meaning start HANA system with operating system (or not)
In other words, we only need to supply the SID and the passwords, all other values take on default parameters.
The log file location is the same as for cockpit. Server only installation takes about 8 minutes.
There is no required post-installation activity as such but making a backup and changing passwords are usual activities. SAP also recommends to disable the SYSTEM and create less privileged users, e.g. USER ADMIN for user administration, BACKUP ADMIN for backups, etc.
SAP HANA Cockpit Manager
Register the database(s) and optionally create a group. This works the same as with previous releases except that we now register a database and not a resource (name change)
SPS 05 alert! New Feature
This is documented in the cockpit administration guide.
Note that if you have yet properly configured the SSL certificates, you do not want to enable SSL as self-signed certificates do not get you very far.
Navigate from the cockpit manager to the cockpit. Note that we are running with issues…
The resource directory is now Database Directory. New graphs have been added for resource consumption, a new column for expensive statement, and views to filter on usage type.
Enter credentials and connect to the database.
System overview is now Database Overview. Like the directory, we can now select a view in the header to filter (monitoring, administration. user management).
The Alerts card informs us that there is one issue with Backups.
The Backups card informs us that there are no backups.
Time to make a backup. Where are those sysadmins when you need them…
On a side note: when we create an instance of SAP HANA Cloud there are zero issues when we access the SAP HANA cockpit (included with the database as-a-service, no need to install or register anything). When we access the database for the first time, a backup will already have been created.
Running SAP HANA 2.0 SPS 05. Mission accomplished.
SAP HANA 2.0 – An Introduction
Just getting started with SAP HANA? Or do have a migration to SAP HANA 2.0 coming up? Need a quick update covering business benefits and technology overview. Understand the role of the system administrator, developer, data integrator, security officer, data scientist, data modeler, project manager, and other SAP HANA stakeholders? My latest book about SAP HANA 2.0 covers everything you need to know.
Get it from SAP Press or Amazon:
Share and Connect
Questions? Please post as comment.
Useful? Give us a like and share on social media.
If you would like to receive updates, connect with me on
- LinkedIn > linkedin.com/in/dvankempen
- Twitter > @dvankempen
|Over the years, for the SAP HANA Academy, SAP’s Partner Innovation Lab, and à titre personnel, I have written a little over 300 posts here for the SAP Community. Some articles only reached a few readers. Others attracted quite a few more.For your reading pleasure and convenience, here is a curated list of posts which somehow managed to pass the 10k-view mile stone and, as sign of current interest, still tickle the counters each month.|
Are there any changes in the way SSO is configured between cockpit and the HANA dB ? Is this cockpit compatible with HANA SPS 04 ?
No changes for SSO. The topic is documented here: Configuring SSO Access to a Database
SAP HANA Cockpit is backwards compatible and includes all SAP HANA 2.0 releases plus SAP HANA 1.0 SPS 12 (see the notes for the minimal revision number for some functionality).
Cockpit is not forward compatible, that is, you cannot use a cockpit installation from 3 years ago to configure persistent memory introduced more recently. SAP recommends to always use the latest version of cockpit.
I will update cockpit and post my feedback too!
Wonderful, Thank you Denys.
Reminds me a lot of the very first HXE installation: Watching the console carefully take the pre answered questions in a small script to automate installation and shorten waiting time to "the promised land".
The installation scripts (e.g. hdblcm.sh) are excellent reading stuff!
Thanks for the update on Cockpit.. Can I create HDI roles for database administration authorization in Cockpit database and import into connected database which doesn’t have XSA and WebIDE installed like S/4 or HANA on suite??
HDI has a SQL interface, so you can run any command you want. There is no relation to the presence of the application server or a specific app. Would this respond to your question?
Not completely though.. With HDI SQL interface can I push database artifacts (database admin HDI roles) from one XSA system (cockpit) to all my HANA systems? if yes any reference to documentation would be appreciated.
Little bit off this topic...I've a general query related to the working of SAP HANA in a distributed environment. Imagine in a two host scenario without a fail-over host where certain tables and/or partitions are assigned to 2nd index server.what happens to these objects in case 2nd host goes out of service?
A distributed system (a.k.a. scale-out or multiple host) principally addresses system limitations (scale-up versus memory and processor requirements).
A distributed system with two hosts is a minimal setup. Three, five, or ten would be move common in particular with one or more standby hosts to address your scenario: host failure. With only two hosts, you would have to size each host to be able to take over the load of the other (i.e. run at 50% load max) or otherwise plan for table unloads and associated performance impact.
High availability with SAP HANA is more commonly obtained with HANA System Replication (HSR or SR). Here we have two identical systems (single or multiple host) in-sync within the same datacenter, zone, or region. In case of failure of the primary site, the secondary site takes over. This can be configured with guaranteed zero data loss and "invisible" to the client.
Thanks for such a wonderful blog. I am new to SAP HANA. I am reading couple of books on installation and administration of HANA 2.0 SPS5. I plan to do some simulated practice of installation of HANA DB and Cockpit , creation of tenant an all, as explained in the video above. Can you please recommend me what should be the minimum memory, RAM size etc that I should look for. As i don't have any extensive specific industrial customer requirement. My exercise is just installation and some admin task purpose.
To install the SAP HANA, express edition on a virtual machine (VM) allocate 8GB for the server-only version (HANA) and 20GB for server+apps (HANA +XSA); in other words, this requires a computer with at least 12GB or 24 GB respectively.
Using a hosted VM on Azure, GCP, AWS, etc., who often have free tier or trial discounts, might provide a good alternative (this is what I usually do).
You might want to look into the SAP HANA Cloud trial as well, no need to install anything!
Thanks a lot Deny. That helps. Is there any free HANA trail license available to play with a full installation simulation
SAP HANA, express edition comes with a free developer license.
You can get yourself a vanilla SUSE Linux VM and install SAP HANA using the binary downoad. The experience is identical as for the platform edition.
Thanks a lot Denys,
The recommendation here https://help.sap.com/viewer/32c9e0c8afba4c87814e61d6a1141280/2.0.040/en-US/c3807913b0a340a99822bf0d97a01da6.html suggested that I sud have 120 GB HDD.
In my case I have the following in my Notebook:
RAM 16GB which I can increase the amount of swap space to at least 32 GB.
But then I have SSD: 475 GB(Free 223 GB)
My qns is will the installation work in this case - SSD instead of HDD and increasing the RAM by sawp
Solid State Disk drives are much faster than mechanical Hard Disk Drivers, no problem there.
However, SAP HANA is an in-memory database. Data needs to be in memory (RAM) not on disk (SWAP).
A computer with 16GB of RAM will require about 4GB for the OS, leaving 12GB to HANA. This will be enough for running the SAP HANA database (server-only) on a VM but not the database with XSA (server+apps)