Skip to Content

SUSE or RED HAT LINUX for SAP HANA on x86 ???

Hi everyone !

We are running ECC 6 EHP7 on NW 749 (non-unicode) and BW on NW 7.5, all on IBM AIX with an Oracle 12.1 DB backend.

Our management has signed us to migrate out of Oracle DB, to SAP HANA.

We are looking to deploy SAP HANA 2.0 on x86.

We have a mature Red Hat Enterprise Linux practice in place, with 25% of all x86 VM's, and growing fast.

However, we are getting signals with regards to SUSE being far superior to support our SAP HANA environment.

We did find 2 items that do give SUSE an edge : large page support and live kernel patching.

Any other items that we should be aware of, on either SLES or RHEL, to run SAP applications overall, and moreover so, SAP HANA ?

We do have IT analysis firms telling us to go with RHEL, but we'd really like to have some reassurance with regards to it being "OK" at the very least.



Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on Jul 16, 2019 at 06:59 AM

    According to note 2235581-SAP HANA: Supported Operating Systems, RHEL and SLES are both supported for HANA and only these two are supported. Technically SAP doesn't have any preference over these two.

    HANA itself doesn't support hugepage or Transparent Hugepage, so I don't see much benefits here.

    Too choose one, you may need to evaluate from maintenance and operating point of view. SAP application specific part can be ignored.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 27 at 02:59 PM

    It's been a long time since this was originally asked, but I'll chip in from experience managing Linux in the enterprise (meaning I didn't just slap it on a spare laptop, I've been responsible for hundreds of Linux hosts on multiple platforms, architectures and hypervisors).

    I managed RHEL for about 12+ years (RHEL 2.1 through 7) and then came back to SLES with v12-15 for the past 2.

    SLES vs. RHEL is a little bit like Portugese vs. Spanish - they're dialects. RHEL puts ifcfg-eth* files in /etc/sysconfig/network-scripts while SLES puts them in /etc/sysconfig/network. SLES uses zypper but RHEL uses yum. With RHEL it's Kickstart and SLES has AutoYaST. The SuSE Manager product is effectively RHN Satellite v5 (technically, it is Spacewalk).

    My point is that any org with competent RHEL admins should not be afraid to invite SLES to the party. We can argue technical merits of each, but to what end? There's pros and cons to both.

    From the business perspective, an SAP shop should (in my opinion) place supportability of the SAP environment at the front of the line. I am aware that tends to favor SLES. That said, having managed both, I don't think the Linux OS vendor should be the driving factor for an SAP shop.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 27 at 03:13 PM

    Thanks David !

    Since my initial post 2 years ago, we have progressed along here, and let me enlighten you as to what our path has been:

    1) position RHEL for all new Linux deployments, so as to leverage existing investments and knowledge

    2) migrate BW databases from AIX/Oracle to SAP HANA on RHEL/x86 (all-VMWARE)

    3) migrate SAP portals and Fiori from AIX to RHEL/x86 (all-VMWARE)

    Now we are about to migrate ECC db from AIX/Oracle to HANA, and to migrate all remaining ECC and BW App Servers to RHEL/x86 (all-VMWARE)

    On the infra side, our experience has been really good, but it's not really complicated. Your success depends on the availability of skilled SAP HANA BASIS.



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.