SAP HANA Hands on tests ( part 3.1 ) : Applying patches to HANA DB
I’m using HANA DB V1.00.82 as a starting point.
I’m performing an update of the existing component using the hdblmgui.
In this first step I am not using the HDB studio HLM embedded interface.
The hana server is a single node one with ECC6 EHP7 running on it ( fresh installation ) .
A few things to know about HANA patches / updates :
There are different kind of patches available for the Hana DB :
– SPS : stands for Support Packages Stacks.
Support packages stacks for HANA will provide corrections and new features or capabilities.
SPS are scheduled and rekeased twice a year.
Updates are strictly downward compatible.
– SPS Revisions :
Contains some individual updates and software corrections available for SAP HANA
Revisions are cumulative and strictly downward compatible.
– Maintenance revision :
Includes only major bug fixes.
These are provided until the next SAP HANA production system verified revision is released. Around 3 months after the release of the next SPS.
Then customers must update to the next SP revision to obtain the new bug fixes.
– Datacenter Service Points:
These are planned 3 months after an SPS release and are versions of SAP HANA that have been run in production enterprise applications at SAP before being released to customer. The DC Service points are released in March and September.
That said, here is my current version of my test hana database :
I’m running HANA Version 1.00 SPS 8 revision 2.
No maintenance revision applied ( or version 00 )
To do a parallel with ABAP Support packages, I would say that :
Datacenter Service Points are rather like SR : ie a verified package that can be applied securely as a whole ( although it is a new concept coming in with HANA ).
Hana Support Packages Stacks make me think of EHPs in the ABAP world : bringing in new features and capabilities for HANA.
SPS revisions are rather like individual ABAP SPs : binging updates and software corrections.
Maintenance revision make me think of SAP Notes : major bug fixes.
Of course there are some differences but it helps me to understand it.
Note : What I would follow as a maintenance strategy, on a personal point of view, on a productive landscape is :
Get my hana db to the latest DC Service point available. In beetween, apply the maintenance revision when needed.
Update to the next DC service point when available.
I’d keep the SPS update if i’m out of solution or clearly require an update to the next SPS ( ie no maintenance revision available nor DC service point in the needed timeframe ) .
This means, in the end , at least schedule an update each 6 months from a DC service point to the next available when possible.
Now we will update from 1.00.82.00.384070. to SPS93 :
– Download the Hana DB software from the SAP market place ( support.sap.com/swdc -> software by a-z index -> H -> hana platform )
– Follow the update guide : SAP HANA Master Update Guide :
1.Stop all processes.
2.Make a system backup if necessary
3. Perform an update.
4.Update the depending components.
5.Perform the post-update steps.
6.Restart all processes.
First stop any applicationn using the HDB .
I had only an ECC running on my HDB then : Stopsap (R3) of the ECC server.
Stop the HDB : HDB stop as htladm
I’ve performed a full system backup ie not only the db but also the VM hosting the HDB. – -> done with veeam once the ECC and HDB are stopped.
Perform the update :
– uncompress the HDB updates in a directory.
– Will update each Hana component individually as if I was applying “a single SP” to each components of my hana DB :
Starting with the Hana core server :
– start the hdblcmgui ( I wanted the GUI ) and perform the update :
At first I wanted to perform the update component by component but it appears that we can patch everything at the same time using the “add component location” button.
Then I updated everything giving the packages location :
All the updates are detected.Then I can continue the update.
Some OS packages required to be updated on the system. As shown in the popup below :
We performed the update and restarted the Hana DB update :
The update finishes O.K.
I restart the HDB only and then proceed with the post update steps :
– Update of the Hana Studio.
You just need to execute the update.
Nothing much to say about it.
My SAP Hana studio is now on version 2.0.11 .
HANA DB Post upgrade steps :
As stated in the Hana update guide :
After an upgrade to a new SAP HANA SPS it is recommended to redeploy the calculation views. For more information, see SAP Note 1962472 – Redeployment of calculation views recommended when upgrading to a new SPS.
We perform these steps :
You can redeploy all views (not only those of type “calculation”) of a package. In HANA Modeler, you can select a repository package and choose “redeploy” via the context menu. This will regenerate the runtime objects of all active obejcts.
With the SAP HANA Studio -> SAP HANA Modeler.
You choose : “Redeploy” and select the packages.
Redeployment is then executed.
You can monitor it :
in the log you can check if everything is O.K :
This part is O.K.
– Update the HDB client for SAP software :
For my ECC server, the hana client is installed by default in /usr/sap/SID/hddbclient folder.
Before updating the client you can check the version used here ( screen from an ECC6 EHP7 ) instance :
We stop the system and perform the client installation :
Unpack the client archive :
As ecc sidadm, go to the folder and start hdbinst :
Restart the ECC and perform a quick verification :
The client is updated.
The system is O.K.
Once everything is done, you can reopen the system.