Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for Oracle E-Business Suite Guide Oracle Solaris Cluster 4.1 |
Installing and Configuring Oracle Solaris Cluster HA for Oracle E-Business Suite
HA for Oracle E-Business Suite Overview
Overview of Installing and Configuring HA for Oracle E-Business Suite
Planning the HA for Oracle E-Business Suite Installation and Configuration
Restriction for the Supported Configurations of HA for Oracle E-Business Suite
Restriction for the Location of Oracle E-Business Suite Files
Determine Which Solaris Zone Oracle E-Business Suite Will Use
Running the AutoConfig Command
Installing and Configuring Oracle E-Business Suite
How to Install and Configure Oracle E-Business Suite
Verifying the Installation and Configuration of Oracle E-Business Suite
How to Verify the Installation and Configuration of Oracle E-Business Suite
Installing the HA for Oracle E-Business Suite Package
How to Install the HA for Oracle E-Business Suite Package
Registering and Configuring HA for Oracle E-Business Suite
How to Register and Configure HA for Oracle E-Business Suite
Verifying the HA for Oracle E-Business Suite Installation and Configuration
How to Verify the HA for Oracle E-Business Suite Installation and Configuration
Upgrading HA for Oracle E-Business Suite
How to Upgrade to the New Version of HA for Oracle E-Business Suite
Understanding the HA for Oracle E-Business Suite Fault Monitor
Probing Algorithm and Functionality
Forms Server in Servlet Mode Probe
Forms Server in Socket Mode Probe
Debugging HA for Oracle E-Business Suite
This section contains the procedures you need to configure HA for Oracle E-Business Suite.
Some procedures within this section require you to use certain Oracle Solaris Clustercommands. Refer to the relevant Oracle Solaris Clustercommand man page for more information about these commands and their parameters.
Perform this procedure on one node of the cluster only.
This procedure assumes that you installed the data service packages during your initial Oracle Solaris Cluster installation.
If you did not install the HA for Oracle E-Business Suite packages as part of your initial Oracle Solaris Cluster installation, go to How to Install the HA for Oracle E-Business Suite Package.
Before You Begin
Ensure that the /etc/netmasks file has IP-address subnet and netmask entries for all logical hostnames. If necessary, edit the /etc/netmasks file to add any missing entries.
# clresourcetype register SUNW.HAStoragePlus # clresourcetype register SUNW.gds
# clresourcegroup create -S -n nodelist pcp-rg
# clresourcegroup create -S -n nodelist c_opmn-rg
# clresourcegroup create -n nodelist ebs-rg
# clreslogicalhostname create -g ebs-rg \ > -h logical-hostname \ > logical-hostname-resource
# clresource create -g ebs-rg \ > -t SUNW.HAStoragePlus \ > -p Zpools=oracle-ebusiness-suite-zspool \ > oracle-ebusiness-suite-hastorage-resource
# clresource create -g ebs-rg \ > -t SUNW.HAStoragePlus \ > -p FilesystemMountPoints=oracle-ebusiness-suite-filesystem-mountpoint \ > oracle-ebusiness-suite-hastorage-resource
Note - If you installed Parallel Concurrent Processing on a cluster file system, when you create the HAStoragePlus resource, specify the scalable resource group that you created in Step 3.
If you installed Clustered OPMN OC4J instances, when you create the HAStoragePlus resource, specify the scalable resource group that you created in Step 4.
If you created a scalable resource group in Step 3, also enable that resource group.
# clresourcegroup online -M ebs-rg If Parallel Concurrent Processing is used: # clresourcegroup online -M pcp-rg
If Clustered OPMN OC4J instances are used, enable that resource group,
# clresourcegroup online -M c_opmn-rg
For complete information about creating and registering a cluster resource for the Oracle Database, refer to Oracle Solaris Cluster Data Service for Oracle Guide.
Note - Before creating corresponding resources, you need to register the SUNW.oracle_server resource type.
# clresource create -g ebs-rg \ > -t SUNW.oracle_Server \ > -p Connect_string=apps/apps \ > -p ORACLE_SID=SID \ > -p ORACLE_HOME=oracle-home \ > -p Alert_log_file=oracle-home/admin/SID \ > _db-logical-hostname/bdump/alert_SID.log \ > -p Restart_type=RESOURCE_GROUP_RESTART \ > -p Resource_dependencies=oracle-ebusiness-suite-hastorage-resource \ > oracle-resource # clresource enable oracle-resource
For complete information about creating and registering a cluster resource for the Oracle Listener, refer to Oracle Solaris Cluster Data Service for Oracle Guide.
Note - The copy_env script is used to copy and format the sid.env to sid_ha.env, which is used by the User_env= parameter in the following example.
Note - Before creating corresponding resources, you need to register the SUNW.oracle_listener resource type .
# cd /opt/SUNWscebs/cmg/util # ./copy_env oracle-home SID_db-logical-host # clresource create -g ebs-rg \ > -t SUNW.oracle_listener \ > -p Listener_name=SID or LISTENER_SID \ > -p ORACLE_HOME=oracle-home \ > -p User_env=oracle-home/SID_db-logical-hostname_ha.env \ > -p Resource_dependencies=oracle-ebusiness-suite-hastorage-resource \ > listener-resource # clresource enable listener-resource
Note - If deploying Oracle E-Business Suite within a zone cluster, you must loopback mount the /var/cluster/logs directory within the zone-cluster node, before registering the Oracle E-Business Suite components.
On all the zone-cluster nodes, perform the following step:
# mkdir /var/cluster/logs
In the global zone where the zone-cluster node is running, perform the following step:
# mount -F lofs /var/cluster/logs zonenode zonepath/root/var/cluster/logs
After all the Oracle E-Business Suite components have been registered, /var/cluster/logs is no longer required within the zone-cluster node. To unmount the previously loopback mounted /var/cluster/logs, perform the following step from the global zone where you loopback mounted /var/cluster/logs:
# umount zonenode zonepath/root/var/cluster/logs
Edit the /opt/SUNWscebs/cmgslr/util/cmglsr_config file and follow the comments within that file. After editing the cmglsr_config file, you must register the resource.
# cd /opt/SUNWscebs/cmglsr/util # vi cmglsr_config # ./cmglsr_register
Note - The variable COMNTOP does not explicitly refer to the COMN_TOP or COMMON_TOP variable. Instead, different values are required depending on the version of Oracle E-Business Suite that is being deployed. See the text below for more details. If you installed Parallel Concurrent Processing, follow these additional editing instructions:
Use COMNTOP=app-base-directory/inst/apps/.
Specify the scalable resource group that you created in Step 3.
Specify a null value for the LH= entry.
COMNTOP=app-base-directory/inst/apps/SID_app-logical-hostname
The following example shows edits of the cmgslr_config file.
RS=ebs-cmglsr RG=ebs-rg LH=ebs-lh HAS_RS=ebs-has COMNTOP=use appropriate COMNTOP APPSUSER=oraapp-user APP_SID=SID VERSION=12.1
Note - A value for the APPS_PASSWD keyword within the /opt/SUNWscebs/cmgslr/util/cmg_config file is optional. You can either specify the password within the /opt/SUNWsebs//cmgslr/util/cmg_config file or within the /opt/SUNWscebs/.${APP_SID}_passwd file on each cluster node as super user. Specifying the password within the /opt/SUNWscebs/.${APP_SID}_passwd file will prevent the password from being viewed by non super users. Refer the comments within the /opt/SUNWscebs/cmgslr/util/cmg_config file for an example.
Note - If deploying Oracle E-Business Suite within a zone cluster, you must loopback mount /var/cluster/logs with in the zone-cluster node before performing this step. See Step 11, for information to loop back mount /var/cluster/logs.
Edit the /opt/SUNWscebs/cmg/util/cmg_config file and follow the comments within that file. After you have edited the cmg_config file, you must register the resource.
# cd /opt/SUNWscebs/cmg/util # vi cmg_config # ./cmg_register
Note - The variable COMNTOP does not explicitly refer to the COMN_TOP or COMMON_TOP variable. Instead, different values are required depending on the version of Oracle E-Business Suite that is being deployed. See the text below for more details. If you installed Parallel Concurrent Processing, follow these additional editing instructions:
Use COMNTOP=app-base-directory/inst/apps/.
Specify the scalable resource group that you created in Step 3.
Specify a null value for the LH= entry.
COMNTOP=app-base-directory/inst/apps/SID_app-logical-hostname
The following example shows edits of the cmg_config file.
If the Oracle Database and Listener are not located within the same global cluster or zone cluster as the Concurrent Manager, you must set an interzone offline restart dependency as follows:
Do not enter any values for the following entries in the cmg_config file: ORASVR_RS= or ORALSR_RS=.
From the global cluster, set the interzone offline restart dependency.
bash-3.00# clrs set -p resource_dependencies_offline_restart=ZONE:DBLSR-RS \ {any_node},ZONE:DB-RS{any_node} -Z CM-ZC CM_RS
Use the following descriptions as a guide:
ZONE – The global cluster or the zone cluster name where the Oracle Database and Listener resources reside.
DBLSR-RS – The Oracle Database Listener resource.
DB_RS – The Oracle Database resource.
CM-ZC – The global cluster or zone cluster name where the Oracle E-Business Suite Concurrent Manager resource resides.
CM-RS – The Oracle E-Business Suite Concurrent Manager resource.
RS=ebs-cmg RG=ebs-rg LH=ebs-lh HAS_RS=ebs-has LSR_RS=ebs-cmglsr VERSION=12.1 COMNTOP=use appropriate COMNTOP APPSUSER=oraapp-user APP_SID=SID APPS_PASSWD=password or empty if using /opt/SUNWscebs/.${APP_SID}_passwd to store the password. ORACLE_HOME=oracle_home CON_LIMIT=50 # # Required for Oracle E-Business Suite version 11.5.10 CU2 or later # ORASVR_RS=ebs1-orasvr ORALSR_RS=ebs1-oralsr
Note - The variable COMNTOP does not explicitly refer to the Oracle E-Business Suite COMN_TOP or COMMON_TOP variable. Instead, different values are required depending on the version of Oracle E-Business Suite that is being deployed. See the text at the end of this step for more details.
For Oracle E-Business Suite Version 12, use COMNTOP=app-base-directory/inst/apps/SID_app-logical-hostname.
Note - If deploying Oracle E-Business Suite within a zone cluster, you must loopback mount /var/cluster/logs with in the zone-cluster node before performing this step. See Step 11, for information to loop back mount /var/cluster/logs.
Edit the /opt/SUNWscebs/frm/util/frm_config file and follow the comments within that file. After you have edited the frm_config file, you must register the resource.
# cd /opt/SUNWscebs/frm/util # vi frm_config # ./frm_register
The following example shows edits of the frm_config file.
RS=ebs-frm RG=ebs-rg LH=ebs-lh HAS_RS=ebs-has COMNTOP=base-directory/sidcomn APPSUSER=oraapp-user APP_SID=SID VERSION=12.1
This step is required only if you are using Oracle E-Business Suite Forms Server in Socket Mode.
Note - The variable COMNTOP does not explicitly refer to the Oracle E-Business Suite COMN_TOP or COMMON_TOP variable. Instead, different values are required depending on the version of Oracle E-Business Suite that is being deployed. See the text below for more details.
For Oracle E-Business Suite Version 12, use COMNTOP=app-base-directory/inst/apps/SID_app-logical-hostname.
Note - If you are deploying Oracle E-Business Suite within a zone cluster, you must loopback mount the /var/cluster/logs directory within the zone-cluster node before performing this step. See Step 11for instructions on loopback mounting the /var/cluster/logs directory.
Edit the /opt/SUNWscebs/frmsrv/util/frmsrv_config file and follow the comments within that file. After you have edited the frmsrv_config file, you must register the resource.
# cd /opt/SUNWscebs/frmsrv/util # vi frmsrv_config # ./frmsrv_register
The following example shows edits of the frmsrv_config file.
RS=ebs-frmsrv RG=ebs-rg LH=ebs-lh HAS_RS=ebs-has COMNTOP=base-directory/sidcomn APPSUSER=oraapp-user APP_SID=SID VERSION=12.1
Note - If deploying Oracle E-Business Suite within a zone cluster, you must loopback mount /var/cluster/logs with in the zone-cluster node before performing this step. See Step 11, for information to loopback mount /var/cluster/logs.
If Clustered OPMN OC4J instances are being deployed, you must specify the OPMN_COMPONENTS=opmn/oacore/forms/oafm. If a Clustered OPMN single Web Entry Point instance is being deployed, you must specify OPMN_COMPONENTS=opmn/http_server. You may also specify OC4J services if required.
For Oracle E-Business Suite Version 12, perform the following:
Edit the /opt/SUNWscebs/opmn/util/opmn_config file and follow the comments within that file. After you have edited the opmn_config file, you must register the resource.
# cd /opt/SUNWscebs/opmn/util # vi opmn_config # ./opmn_register
The following example shows the edits of the opmn_config file.
RS=ebs-opmn RG=ebs-rg LH=ebs-lh HAS_RS=ebs-has VERSION=12.1 COMNTOP=app-base-directory/inst/apps/SID_app-logical-host APPSUSER=oraapp-user APP_SID=PROD APPS_PASSWD=apps OPMN_COMPONENTS=all
If you created a scalable resource group in Step 3, also enable that resource group.
# clresource enable -g ebs-rg + If Parallel Concurrent Processing is used: # clresourcegroup online -eM pcp-rg
If you used Clustered OPMN OC4J, enable that resource group.
# clresourcegroup online -eM c_opmn-rg