Skip to Content
Author's profile photo Jens Gleichmann

HANA maintenance strategy – the customer’s perspective

Hi experts,

this week I participated the “DSAG Technologietage” (German speaking user group – technology days) in Hamburg, Germany. There was one session which was pretty interesting and completely different from all others: „WIR FÜR UNS – DSAG-interne Diskussion:Gerede/Gerüchte zum Thema „HANA“ => translated „ we in private – DSAG – discussion: repute / rumor around the topic HANA“

It was not a classic speaker – audience session. The audience were parted into 3 groups. Every group got a question to discuss it on the flip chart.

#1 Pro/Cons: The future without oracle in connection with SAP

#2 What do I know about HANA?

#3 What will I do if my company will implement HANA?

The results were discussed all together and I wondered about some questions and the nescience.

Now I’m familiar with the technical topic HANA since the last 3 years. I’m administrating oracle databases since 9i – so I know both databases pretty good. But I was shocked that since HANA was released in 2010/2011 (“SanssouciDB”) the people know so less about whole truth. Although the last 2-3 years SAP talked about nothing else more than HANA.

The audience included I think 80-90% DBA’s (mostly Oracle). Employees of any vendor had to leave the session to guarantee a free discussion. The first moment I wondered about this rule, but at the end of the session it was a good decision to talk freely. Don’t panic there was no bashing against any vendor 😉

There were a lot of questions, just some of them:

  • How to handle mixed business oracle/HANA
  • Support: OSS + metalink => future? Only OSS?
  • Oracle tools (RMAN/Dataguard/brtools/Grid) => counterparts with HDB?
  • Maintenance strategy for HDB
  • S/4 on oracle?
  • Releasing the command pool of HDB for adapting it to the “any DBs”

This discussion inspired me to start the discussion about the maintenance strategy. If you are interesting in one of the other topics, I will create another

I will point out in this blog the questions maintenance strategy. Not the normal details which we can all find by our self via google, and the notes. I will just highlight and critical scrutinize the current strategy.

Maintenance strategy

Some facts to give you a briefly overview:

  • For Productive systems are recommended to use the DSP (DataCenterServicePoint – a long term successful test with SAP own productive systems; duration: 2+ weeks) or a newer revision within the same SPS
  • After release of the new SPS (e.g. SPS11) there are only maintenance revisions released for the old SPS (SPS10 with 102.x) for the next 3 months
  • Every 6 months RTC (release to customer) => new SPS
  • Certifications to administrate and install HANA databases which are only valid for 3xSPS => 3x6month => 1,5years after this period you have to recertify yourself on the latest release


Most of the systems which I have administrated could only be maintained with a new patchset once a year, because the testing effort for the application teams are too long to update/upgrade the system, activate new features and verify the functionality. You have to block this people for a long period besides their normal business tasks + projects.

Now you get only 9-months support for your revision. Ok 9 months are short but maybe ok for the most companies. But wait a minute – you have to wait until the DSP is released to test and verify it for your productive system. So this are 6 months minus testing maybe 4-5months. The technical part is pretty easy but the application team are testing the whole year – nothing else! Ok now we shift some application logic from the ABAP application server with CDS (Core Data Services) down to the database. So I have also the responsibility to do regression tests!

After the 3months maintenance revision period, you have to update the system to a newer SPS because no more fixes will be available for it. So if you have an issue there will be no downport to this revision after this period of time, anxious or?

++#Update 02.11.2016#++
New maintenance strategy starting with SPS12

Maintenance starts with RTC of SPS12 May 2016 and ends May 2019 (3 years)


  • SAP HANA SPS 12 customers who do not need new functionalities can apply Maintenance Revisions to their installations for a period of 3 years
  • 3-years maintenance is currently available for SAP HANA SPS12 only
  • At any point in time customers can decide to adopt a newer SAP HANA release, as all SAP HANA releases are backward compatible
  • the 3-years maintenance will be automatically covered by existing and new contracts at no extra cost
  • Mature applications that do not require new functionalities benefit the most from the 3-years maintenance offered with SAP HANA SPS12. These include SAP Business Suite and SAP Business Warehouse
  • New innovative applications benefit the most from the new SAP HANA functionalities that are delivered through SPSs . S/4 HANA customers also should consider adopting the most recent SAP HANA release as new S/4HANA capabilities are often powered by the newest SAP HANA innovations.

++#Update End#++


++#Update 22.03.2016#++

After 8 weeks I have got an answer from SAP education team:

“The certification validity is the release time of the SPS/quarter”

=> This means you have to substract the release time of a SPS from the exam release time:

++#Update End#++

The latest release is SPS11 which was released at the end of 2015. A training and a certification are still only available for SPS09 (E_HANAINS151). So there is no one for SPS10. SPS11 is going to be released in the next months. I have send an email to sap education to clarify from which date a HANA certification is valid (still no answer since 4 weeks):

– From the date I passed the exam?

– From the date the SPS which the certification based on => so the release time of the SPS (correct answer)

++#Update 22.03.2016#++

The C_HANA_INST exam is not available any more in 2016! This will be covered in C_HANA_TEC_xx

For C_HANA_TEC_11 you have to pass C_HANA_TEC_10.

SAP HANA Training and Certification Program 2016

++#Update End#++

So when the exam is available it is possible that one or two newer SPS were released in the meantime. This results in a certificate which is only valid for 6-12 months! How many certifications have you passed for oracle, db2, mssql, maxdb or Sybase? I think max. two – if any. However, but not every year! To install a productive HANA DB you have to be certified.

I know HANA is real fast moving technology with a mass of developers behind and with every release a ton of new features. I love to work with it, test new features and of course discover new bugs. But it has to be fit in the maintenance strategy of the customers. The current strategy is not clearly defined and with more logic on the HDB itself and the coming S/4 it will getting more complex. (still after the updates the maintenance is still not compareable with e.g. Oracle or DB2)

What is your experience and strategy with HANA and the other “any DBs”?


Best Regards,

Jens Gleichmann


Maintenance strategy:

2021789 – SAP HANA Revision and Maintenance Strategy

1948334 – SAP HANA Database Update Paths for Maintenance Revisions

Certifications 2015: SAP HANA Education – Course & Certification Program 2015

Certifications 2016: SAP HANA Training and Certification Program 2016

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Stefan Koehler
      Stefan Koehler

      Hi Jens,

      great blog post. So the basic statement about SAP HANA is "After the patch is before the patch". The customers must have a real obsession about patching, if they accept this kind of product life cycle.

      Just a little intellectual game by adopting this approach to Oracle. So you would have a patch set (let's call it), but this patch set is only valid for 6 months and you would only get support and patches for this patch set for 9 months in sum (so basically 3 PSUs / SBPs). That's ridiculous compared to the current available RDBMS life cycle of Oracle (e.g. MOS ID #742060.1).



      Author's profile photo Florian Henninger
      Florian Henninger

      Hi Jens,

      the question is moreover, what is the process to get a patch.

      So just let me share some thoughts about it:

      - Can I patch my db without having a supportwindow/downtime?

      - What do I need to test/validate/do before patching?

      - How is the backup-strategy in case something went wrong?

      to summarize these questions:

      How much do I have to pay for a patch all cost included?

      These are just a few questions missing to draw a big picture.

      My personal opinion on that topic:

      If this is less or at least the same cost where is the problem.

      And having a certificationupdate every 18 Month isn't that bad, is it? I would love to stay always "up-to-date" with new features if this doesn't end in a massive invest-problem for my company.

      Additional to that, one further question:

      - Where do you got your digits for testing approved. Do you run a S/4 System in productive use right now and have done there severel upgrades?

      Upgrades without upgrades of the application-side doesn't have a deep impact on the testing is my experience, so I wonder that you have such a hugh digit.


      Author's profile photo Stefan Koehler
      Stefan Koehler

      Hi Florian,

      > Upgrades without upgrades of the application-side doesn't have a deep impact on the testing is my experience, so I wonder that you have such a hugh digit.

      As far as i can see you are a developer and so you might be right in case of application adaptation. However look at this topic from an operational perspective. Would you like to run your critical SAP system (well SAP claims that HANA is already mission critical ready) in a non tested environment? Just to mention a few key points from an operational perspective like Backup/Recovery, HA (system replication), etc.

      In addition you always have to do some performance regression tests, unless the database vendor guarantees that no change in behavior is included in a patch set. For example Oracle is doing this with its PSUs (quarterly patches) - it only includes security and wrong result set fixes, but it does not change the optimizer, etc.. However if you install a whole patch set (e.g. like,, etc.) then you have to do the whole test cycle to validate performance. Customers are very critical in this point at least when the performance dropped drastically the first time after a patch set apply.

      However as SAP HANA develops so quickly - SAP also works on optimizations and  transformations, etc. all the time with each SPS. So no guarantee here.



      Author's profile photo Florian Henninger
      Florian Henninger

      Hi Stefan,

      yes, I'm a developer 😛 and yes of course, I'm not standing that hard at a point that everything is fine and noone has to worry, but exact this point is one of the biggest points customers was waiting for.

      That new technologies  and possibilities are having an impact on the business. This will be just possible if the upgrades aren't years away.

      As a developer I also worry today, that I have such a lot of different systems with different releases and I can't use everything I want to use (for example ADT-Tools).

      I can understand that there are some other pain-points on the operational perspective which I can't cover or even imagine, but I'm a first row soldier also on listen to the customers need and also I see how SAP runs his systems in the cloud and if I'm right, the cloud-operational side is covered by SAP and one of the major points to move there is that the upgrades will be there delivered in this short time.

      That brings me to the question, if this is really that much testing and out of that this big impact how is SAP doing the upgrades? They even can't know every single custom-developed application, even if they want to it wouldn't be possible (and I'm pretty sure they also can't test every application of their own without automation).

      I'm pretty sure, SAP has figured this out before investing that massive in cloud-solutions and also in cloud-hosting.

      I don't know that much about patching systems on an operational point of view, but I'm pretty sure there is a strategy available. Maybe someone can jump in and bring some more light to the dark spots here.

      Maybe (or also 😉 ) it is a gap at the application side and we need to have unit test/ecatt (automation of testing) improved and delivered with every application we are building, that the testing will get better and a lot faster.


      Author's profile photo Jens Gleichmann
      Jens Gleichmann
      Blog Post Author

      Hi Florian,

      thanks for your comment and your questions.

      - Can I patch my db without having a supportwindow/downtime?

      => Yes, it's possible with System Replication and the Kernel DBSL suspend feature

      => just check page 16 in this document: SAP HANA: Revision Strategy | SCN

      - What do I need to test/validate/do before patching?

      => you should test and check with the new Revision/SPS the following:

      • 2-4 weeks in quality assurance system
      • new parameter and side effects coming with
      • test all CDS objects, HANA modeled objects
      • SAP HANA: Revision Strategy | SCN  => page 11

      - How is the backup-strategy in case something went wrong?

      => shortly before maintenance you should take a backup of the DB and the config files

      => if something went wrong the fallback is to to reinstall the old revision with its configuration + recovery of the last valid backup (may be PTR to roll forward to exact the point of maintenance)

      => if your system is on vmware you also shutdown the application + db, take snapshot and revert back to it

      => it depends on your landscape, backup strategy and architecture of the system

      I'm with you that a certification update is not a bad thing. It is a fast moving technology and if you compare for example SPS7 with SPS10 => there are a ton of new tools and the way you install and update the components.

      But should it be a must have? For some people (e.g. freelancer) and companies it could be more a time issue than a financial impact. You should be well prepared for the exam. It consists of 80 (associate) + 40 (install) questions. You can visit a delta training or collect the details by yourself. However one week + the days for the exam are gone. If you have 5 DBA's and everyone should administrate and install a HANA DB, you have a lot of off time for this people. Normally a trainings contingent of the company should absorb this, but you have to plan this every 18 months. For other DBs this was not a must have - consider this.

      - Where do you got your digits for testing approved. Do you run a S/4 System in productive use right now and have done there severel upgrades?

      => in this context you mean the 4-5months? So meant 1-2months fort testing before you should upgrade your productive system. It depends (lovely phrase of consultants) on your system and its complexity. If you are orienting on the defaults, your testing effort is less. But if you have a lot of own development and CDS views, models and so on the testing effort will be higher. Currently there are only a few S/4 systems because not for all business solutions and branches are solutions on S/4 available. But this will come in the near future more and more 😉

      - Upgrades without upgrades of the application-side doesn't have a deep impact on the testing is my experience, so I wonder that you have such a hugh digit.

      => as Stefan already mentioned, if this are just fixes and no new features with adapting core functions e.g. delta merge algorythm, execution plans, set of commands inside HANA (=> this fits for the maintenance revisions) => you don't have to do big regression tests.

      Hope this answers your questions 🙂



      Author's profile photo Florian Henninger
      Florian Henninger

      Hi Jens,

      thanks for your reply. Nice to see a point of view I haven't covered before.

      Testing the CDS could be an easy thing if there are unit-test available, so I believe it is a thing, which need to be covered together with the applicationside.

      The applicationside invest a littlebit more on having good automation of testing will take away this painpoint on your side.

      So (also a lovely phrase of consultants 😉 ) it is up to the customer to not see only the shorttime invest of such testing-solutions.

      Regarding to the certification I can understand your point of view. On the other hand there is the need to guarantee that we (all of us, developers, consultants, basis-guys and so on) are adapting the new possibilities and a lot is also working in an old fashioned way which might not be clear to the customer.

      So how would you cover the need, that new functions are used by the people which are responsible for the systems? At the moment I don't see another way to get the features delivered without the certifications.

      I'm with you that this might be not a perfect solution right now...