In June 2010, Oracle and SAP first announced they were working together on certifying Oracle’s Exadata database machine for SAP applications, according to IDG News Service. The work mattered to companies that ran SAP software on Oracle databases and wanted to know whether Exadata’s hardware and software would be supported.
The announcement fed a wider discussion that summer about handling large data volumes in transactional enterprise applications. Product lifecycle management bloggers asked at the time whether their field should care about the same scaling problem.
What the two companies agreed
Exadata is Oracle’s data-processing system, which combines specialised hardware and software around the Oracle database. IDG News Service described it as a major focus for Oracle in the years around 2010. The second generation, Exadata X2, was built for both transactional and analytic workloads.
SAP had to certify any platform before it could support SAP applications on it. For customers that meant a certified Exadata would let them keep an Oracle database under SAP software and have SAP support it. Oracle’s own FAQ on the subject presented Exadata as close to essential for SAP’s installed base, since many SAP customers ran several Oracle databases beneath several SAP applications.
The competing pressure on Oracle
The collaboration took place while SAP was reducing its dependence on Oracle’s database. SAP had recently launched HANA, an in-memory computing platform backed by several hardware vendors. It had also bought Sybase, which it ran as an independent subsidiary, and it moved to certify the Sybase Adaptive Server Enterprise (ASE) database for Business Suite. IDG News Service reported that SAP planned to offer ASE as a migration option for SAP shops running Oracle.
At its Sapphire conference in May of a later year, SAP officials described HANA as able to handle transaction processing as well as analytics. IDG News Service noted, though, that HANA would take some time to replace Oracle for running applications such as Business Suite.
Certification arrives
The certification came after the June 2010 announcement. IDG News Service reported that Exadata X2 machines were certified to run SAP applications, with the certification valid from a Friday according to SAP’s website. It covered products based on NetWeaver 7.x and certified for Oracle Database 11g Release 2.
Oracle’s September 2013 white paper on SAP NetWeaver and Exadata went further. It stated that all SAP products from NetWeaver 7.0 onward were certified to use the Exadata Database Machine. It set out the setup steps, including the BR*Tools administration utilities, which needed version 7.20 (patch 18) or later because older versions did not fully support Automatic Storage Management, a requirement for Exadata. The paper said Oracle regularly tests and certifies the SAP bundle patch for Exadata and makes it available to SAP customers through the SAP Service Marketplace.
What happened next
Later Exadata generations were certified too. Oracle announced that SAP applications based on NetWeaver 7.x were certified on Oracle Exadata Cloud Service, with Oracle Database 12c Release 1 (12.1.0.2) and Release 2 (12.2.0.1) supported. An Oracle documentation paper for the cloud service lists Oracle Database 19c and 18c, and says Oracle Database 11g Release 2 is not supported there. It also says SAP application servers cannot run on the Exadata compute nodes.
Oracle’s SAP solutions page states that, as of February 2025, the Exadata X11M-2 and X11M-8 systems are certified for SAP applications. It adds that Oracle Databases for SAP Business Suite and NetWeaver 7.x can run on Exadata X11M on-premises and on Exadata Cloud@Customer X11M. Oracle presents the Cloud@Customer option as aimed at SAP customers who want cloud benefits but cannot move to the public cloud for operational, business, regulatory or legal reasons. SAP Note 2614028 is the reference for the current status.