X

News, tips, partners, and perspectives for the Oracle Solaris operating system

SAP & Oracle - Multitenant option on 12c with Solaris

Guest Author

Oracle and SAP share a multitude of enterprise customers who want to run
their SAP solution on Oracle hardware with Oracle Database 12c.  This
blog is part of Oracle’s ISV engineering effort to implement joint integration projects to ensure the latest technology is
available for SAP and Oracle solutions.  

** ANNOUNCING ** Customers running Netweaver-based SAP applications on Oracle Database 12c can now register as early Oracle Multitenant adopters (more info)

So, what is “Multitenant”,  and why should you care?!

IT
organizations are severely challenged to achieve high levels of
database consolidation density without incurring major development and
administrative overheads.  Oracle Multitenant introduces a new
architecture to Database 12c, which enables easy consolidation of
multiple databases without the effort of changing the underlying
applications. 

There are many benefits to this, but key is that
standardizing on fewer moving parts in the data center helps to maximize
the value of consolidation.  As the world moves toward a
cloud-computing model, primary to that journey is database consolidation. 
This new architecture delivers all the savings of managing many
databases as one, yet also retains the isolation and resource
prioritization of having separate databases.  Oracle Multitenant also
enables rapid provisioning and upgrades, and fully complements other
options including Oracle Real Application Clusters and Active
DataGuard.  In a nutshell, it tackles major database consolidation
issues.  Read this product brief for more details.

Now, lets talk about of how you install the Multitenant option.

SAP systems can be installed on Oracle Multitenant databases with SWPM (Software Provisioning Manager).  We collected first-hand experience of Oracle Multitenant by installing two SAP systems on a SPARC Solaris server.


 - The container database is: MTT.

 - The corresponding pluggable databases are: QO1 & QO2


Before installation, prepare the groups (oinstall, dba, oper, sapsys, sapinst), users (oracle, oramtt, sapadm, qo1adm, qo2adm), projects (MTT, QO1 & QO2), and kernel parameters for user root. Please refer to SAP note 724713 for projects and kernel parameters on Oracle Solaris 10 & 11 systems.

1. The first SAP system "QO1" is installed with the container database "MTT" and pluggable database "QO1".

+++++++++++

Start sapinst, enter the required information as usual until the screen „SAP System Database“. Enter the container database MTT as „Database ID (DBSID)“ on this screen, and then continue as usual.


+++++++++++

Download the latest SAP Kernel Packages and other required archives from SAP Support Portal. On the screen „Software Package Browser“, enter the absolute path to the download folder.

+++++++++++

On the screen „Oracle Multitenant Database“ choose the option „CDB and PDB“.

+++++++++++

Perform the remaining steps of SAP installation as usual.

2. The second SAP system QO2 is installed with pluggable database QO2 within the existing container database MTT

Start the sapinst as usual, on the screen „Oracle Database“, choose „Install Additional Pluggable DB in Existing Container DB“.

+++++++++++

On the screen „Oracle Multitenant Database“, choose „PDB“.

s

+++++++++++

Perform the remaining steps of SAP installation as usual.

SAP and Oracle will continue to provide customers with additional joint statements and details at www.oracle.com and www.sap.com.  For more information, please refer to:

 - Oracle for SAP:  http://www.oracle.com/sap

Join the discussion

Comments ( 1 )
  • Satish Kumar Sunday, July 22, 2018
    Hi,
    Nice blog.
    1. Is the single instance on filesystem the only supported option?

    2. Is RAC + CDB > supported for SAP systems? if yes, from when?

    Best Regards,
    Satish Kumar
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.