X

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

  • December 17, 2018

Oracle Solaris Cluster support for Oracle E-Business Suite 12.2.8

Neil Garthwaite
Principle Software Engineer

We are very pleased to announce further support for Oracle E-Business Suite 12.2.8 on the following Oracle Solaris Cluster versions:

  • Oracle Solaris Cluster 4.3 SRU 3 or later on Oracle Solaris 11.3
  • Oracle Solaris Cluster 4.4 or later on Oracle Solaris 11.4

Deploying Oracle E-Business Suite 12.2 with Oracle Solaris Cluster provides the ability to take advantage of the zone cluster feature to provide security isolation, application fault isolation as well as individual resource management within a zone cluster.

Note, Oracle offers the ability to license much of its software, including the Oracle Database, based on the quantity of CPUs that will run the software. When performance goals can be met with only a subset of the computer's CPUs, it may be appropriate to limit licensing costs by using a processor-based licensing metric. The document Hard Partitioning With Oracle Soalris Zones explains the different Solaris features that can be used to limit software licensing costs when a processor-based metric is used.

In the deployment example below, the Oracle E-Business Suite 12.2.8 DB-Tier and Mid-Tiers have been deployed within separate zone clusters.

Furthermore, the Primary Application Tier and subsequent WebLogic Administration Server have been installed within an Oracle Solaris Cluster failover resource group using a logical host.

What this means is that if the physical node or zone cluster node hosting the Primary Application Tier and subsequent WebLogic Administration Server fails then Oracle Solaris Cluster will fail over the Primary Application Tier to the other zone cluster node.

Oracle Solaris Cluster will detect a zone cluster node or physical node failure within seconds and will automatically fail over the logical host to another zone cluster node where the Primary Application Tier services are automatically started again. Typically, the WebLogic Administration Server is available again within 2-3 minutes after a zone cluster node or physical node failure.

The following diagram shows a typical Oracle E-Business 12.2 deployment on Oracle Solaris Cluster 4.3 with Oracle Solaris 11, using Oracle Solaris Zone Clusters.

With this deployment example, after Oracle E-Business Suite 12.2.8 was installed and configured on Oracle Solaris Cluster 4.3, a version update was performed from the latest version of 4.3, using the rolling upgrade method, to Oracle Solaris Cluster 4.4 and Oracle Solaris 11.4 in order to take advantage of new features offered by Oracle Solaris Cluster 4.4. One new feature is the support for immutable zone clusters.

Once running on Oracle Solaris Cluster 4.4 and Oracle Solaris 11.4, both Oracle Solaris zone clusters were configured as immutable zone clusters in order to restrict access with read-only roots. A read-only zone cluster can be configured by setting the file-mac-property. Using a read-only zone cluster root expands the secure runtime boundary.

The following example provides simple steps to configure immutable zone clusters for db-zc and app-zc.

Note, a zone cluster node reboot is required to implement the immutable zone cluster configuration. However, in order to maintain the availability of Oracle E-Business Suite 12.2.8 services a rolling zone cluster node reboot is performed.

As shown within the diagram above, the Primary Application Tier contains the HTTP Server which represents the single Web Entry Point. As such, when an app-zc zone cluster node is rebooted that is running the HTTP Server a small HTTP Server interrupt will occur. Typically, this takes less than 1 minute before Oracle Solaris Cluster has restarted the HTTP Server on the surviving zone cluster node for app-zc. Note, already connected clients may not notice that small outage if they did not hit enter, during that outage, as their session will remain connected.

Verify that zone clusters db-zc and app-zc are running on each physical node

root@node1:~# clzc status db-zc app-zc
=== Zone Clusters ===
--- Zone Cluster Status ---

Name     Brand     Node Name   Zone Host Name   Status   Zone Status
----     -----     ---------   --------------   ------   -----------
db-zc    solaris   
node1       vdbnode1         Online   Running
                   
node2       vdbnode2         Online   Running

app-zc   solaris   
node1       vappnode1        Online   Running
                  
node2       vappnode2        Online   Running
root@
 node1:~#

Configure immutable zone clusters for db-zc and app-zc

root@node1:~# clzc configure db-zc
clzc:db-zc> set file-mac-profile=fixed-configuration
clzc:db-zc> exit
root@node1:~#
root@node1:~# clzc configure app-zc
clzc:db-zc> set file-mac-profile=fixed-configuration
clzc:db-zc> exit
root@node1:~#

Selectively reboot each db-zc zone cluster node as an immutable zone cluster node

Verify that that the Oracle RAC Database instances are running.

root@node1:~# zlogin db-zc 'su - oracle -c "srvctl status db -d vis"'
Oracle Corporation      SunOS 5.11      11.4    November 2018
Instance VIS1 is running on node vdbnode1
Instance VIS2 is running on node vdbnode2

root@node1:~#

Reboot zone cluster db-zc on node1.

root@node1:~# clzc reboot -n node1 db-zc
Waiting for zone reboot commands to complete on all the nodes of the zone cluster "db-zc"...
root@node1:~#

Once complete verify that the Oracle RAC Database instances are running, as shown above, before continuing.

Reboot zone cluster db-zc on node2.

root@node1:~# clzc reboot -n node2 db-zc
Waiting for zone reboot commands to complete on all the nodes of the zone cluster "db-zc"...
root@node1:~#

Once complete verify that the Oracle RAC Database instances are running, as shown above, before continuing.

Selectively reboot each app-zc zone cluster node as an immutable zone cluster node

Verify that that Oracle E-Business Suite 12.2.8 services  are running.

root@node1:~# clrs status -Z app-zc

Reboot zone cluster app-zc on node1.

root@node1:~# clzc reboot -n node1 app-zc
Waiting for zone reboot commands to complete on all the nodes of the zone cluster "app-zc"...
root@node1:~#

Once complete verify that that the Oracle E-Business Suite 12.2.8 services  are running, as shown above, before continuing.

Reboot zone cluster app-zc on node2.

root@node1:~# clzc reboot -n node2 app-zc
Waiting for zone reboot commands to complete on all the nodes of the zone cluster "app-zc"...
root@node1:~#

Once complete, immutable zone clusters providing read-only roots are now underpinning Oracle E-Business Suite 12.2.8 services.

As noted above, Oracle Solaris Cluster provides the ability to take advantage of the zone cluster feature to provide security isolation, application fault isolation as well as individual resource management within a zone cluster. In this context, it is possible to consolidate other Oracle E-Business Suite deployments within separate zone clusters.

A future article will expand this deployment example to include Business Continuity for Oracle E-Business Suite 12.2. While there are many use cases that could be considered, a largely passive standby site, within a primary and standby Disaster Recovery configuration, could be used for development / test Oracle E-Business Suite deployments.

Those deployments would be quiesced before a takeover or switchover to a standby site of the production Oracle E-Business Suite 12.2.8. Such other Oracle E-Business Suite deployments could be deployed within separate zone clusters and would be isolated from the production Oracle E-Business Suite 12.2.8 deployment.

For more information please refer to the following:

Oracle Solaris Cluster 4.4 Release Notes

How to Deploy Oracle RAC on an Exclusive-IP Oracle Solaris Zones Cluster

How to configure a Zone Cluster to Be Immutable

Oracle Solaris Cluster Data Service for Oracle E-Business Suite as of Release 12.2 Guide

Hard Partitioning With Oracle Solaris Zones

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha