Patch-ID# 118328-04

NOTE:
***********************************************************************
READ THE TERMS OF THE AGREEMENT ("AGREEMENT") IN THE LEGAL_LICENSE.TXT
FILE CAREFULLY BEFORE USING THIS SOFTWARE. BY USING THE SOFTWARE, YOU
AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE
TERMS, PROMPTLY DESTROY THE UNUSED SOFTWARE.
***********************************************************************

Keywords: sunwsc9ias
Synopsis: Sun Cluster 3.0/3.1: SUNWsc9iAS patch
Date: Mar/13/2006


Install Requirements: See Special Install Instructions                      
                      
Solaris Release: 8 9 10

SunOS Release: 5.8 5.9 5.10

Unbundled Product: Sun Cluster

Unbundled Release: 3.1/3.0

Xref: 

Topic: Sun Cluster 3.0/3.1: SUNWsc9iAS patch

Relevant Architectures: sparc

BugId's fixed with this patch: 5108767 6190002 6190005 6219038 6260735 6382811 6382813 6382825

Changes incorporated in this version: 6382811 6382813 6382825

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch: 

Patches required with this patch: 

Obsoleted by: 

Files included with this patch: 

/opt/SUNWsc9ias/bin/control_oas
/opt/SUNWsc9ias/bin/functions
/opt/SUNWsc9ias/bin/probe-em
/opt/SUNWsc9ias/bin/probe-oidldap
/opt/SUNWsc9ias/bin/probe-oidmon
/opt/SUNWsc9ias/bin/probe-opmn
/opt/SUNWsc9ias/bin/start-em
/opt/SUNWsc9ias/bin/start-oidldap
/opt/SUNWsc9ias/bin/start-oidmon
/opt/SUNWsc9ias/bin/start-opmn
/opt/SUNWsc9ias/bin/stop-em
/opt/SUNWsc9ias/bin/stop-oidldap
/opt/SUNWsc9ias/bin/stop-oidmon
/opt/SUNWsc9ias/bin/stop-opmn
/opt/SUNWsc9ias/etc/SUNW.9ias
/opt/SUNWsc9ias/util/10gas_register
/opt/SUNWsc9ias/util/9ias_register

Problem Description:

6382825 Oracle Application Server SC Agent incorrectly probes opmn for ALL components
6382813 Sun Cluster Data Service for Oracle Application Server documentation needs updating
6382811 Oracle Application Server support for Solaris 10
 
(from 118328-03) 
 
6260735 Agent requires support Oracle 10gAS v10.1.2
 
(from 118328-02) 
 
6219038 Dummy RTR file requires #% SERVICE_NAME entry for package upgrade
 
(from 118328-01) 
 
5108767 Validation of 10gAS fails when running /opt/SUNWsc9ias/util/10gas_register
6190002 Avoid potential unnecessary name service lookup through simple commands
6190005 Probe for emctl needs correct /var/opt/oracle/emtab

Patch Installation Instructions:
-------------------------------- 
There are three (3) possible procedures for installing patches on 
Sun Cluster 3.0 and 3.1.  The proper method to use and any additional
instructions, for this patch are specified below in the "Special
Install Instructions" section.
 
Refer to the chapter entitled "Patching Sun Cluster Software and 
Firmware" in the Sun Cluster 3.0/3.1 System Administration Guide
for a description of the different install processes and instructions 
on how to install Sun Cluster 3.x patches.
 
For Solaris 8 release, refer to the man pages for instructions on 
using 'patchadd' and 'patchrm' scripts provided with Solaris.

Special Install Instructions:
----------------------------- 
 
NOTE 1:  Follow "How to Apply a Non-Rebooting Sun Cluster Patch" in the Sun
         Cluster 3.0/3.1 System Administration Guide.
 
NOTE 2:  If this patch is being applied to a Solaris 10 system, the patch must be
         applied to the global zone only by using the -G option for patchadd, e.g.
 
         <global zone># patchadd -G 118328-04
 
         To remove the patch from a Solaris 10 system, you must also use the -G
         option for patchrm, e.g.
 
         <global zone># patchrm -G 118328-04
 
 
NOTE 3:  Notes about bugid 6382813:
 
         The documentation change listed below applies to an installation of Oracle
	 Application Server v9.0.2 or v9.0.3 only.
 
	 If you are installing Oracle Application Server v10.1.2 on Solaris 10 you
	 must perform Steps 1-3 and then follow Oracle's Metalink Note: 330016.1. 
	 Afterwards you must perform Step 8.
 
	 The Sun Cluster Data Service for Oracle Application Server documentation
	 needs to be updated to correctly reflect any additional steps when applying
	 a core patchset for Oracle Applications Server. 
 
	 These additional steps only affect installations of Oracle Application Server
	 v9.0.2 or v9.0.3. If you are installing Oracle Application Server v9.0.4 or 
	 later, these additional steps do not apply.
 
	 You will need to substitute your values for entries with <>.
 
	 When specifying the <logical host>, you must specify the short name for the 
	 logical host and not the fully qualified name.
 
 	 How to Install and Configure Oracle Application Server
	 ------------------------------------------------------
 
	 The following text reflects condensed documentation for the installation of 
	 Oracle Application Server v9.0.2 and the 9.0.2.3 Core Patchset.
 
	 1. Boot all nodes outside of Sun Cluster
 
	    scshutdown -y -g0
	    boot -x
 
         2. Take ownership of the SVM Diskset or VXVM Diskgroup and mount the filesystem
 
	    For SVM, 
 
		metaset -s <dg> -f -C take
	   	mount <filesystem>
 
	    For VXVM, 
 
		vxdg -c import <dg>
		vxdg -g <dg> startall
	   	mount <filesystem>
 
         3. Plumb the logical IP address, being used for Oracle Application Server installation
 
	    ifconfig <interface> addif <logical host> up
 
         4. As root on each node in the cluster, prepare the logical host interpositioning
 
	    cd /opt/SUNWsc9ias/lib
	    cp libloghost_32.so.1 /usr/lib/libloghost_32.so.1
	    cp libloghost_64.so.1 /usr/lib/sparcv9/libloghost_64.so.1
 
	    cd /usr/lib/secure
	    ln -s /usr/lib/libloghost_32.so.1 libloghost_32.so.1
 
	    cd /usr/lib/secure/sparcv9
	    ln -s /usr/lib/sparcv9/libloghost_64.so.1 libloghost_64.so.1
 
         5. As the Oracle Application Server userid, execute the runInstaller program
 
	    su - <userid>
	    LD_PRELOAD_32=libloghost_32.so.1
	    LHOSTNAME=<logical host>
	    export LD_PRELOAD_32 LHOSTNAME
 
	    cd <install directory> 
 
	   ./runInstaller
 
	    Follow the OUI screens as required. After installing the software, 
	    you will be prompted to execute ${ORACLE_HOME}/root.sh script, 
            before the OUI will continue with the configuration assistant.
 
	    Before executing ${ORACLE_HOME}/root.sh perform Step 6.
 
         6. Before executing ${ORACLE_HOME}/root.sh script
 
	    cd ${ORACLE_HOME}/Apache/Apache/bin
	    vi apachectl
 
	    Before the PIDFILE entry, add the following lines
 
	    LD_PRELOAD_32=libloghost_32.so.1
            LHOSTNAME=<logical host>
            export LD_PRELOAD_32 LHOSTNAME
 
         7. As root, execute the ${ORACLE_HOME}/root.sh script and continue with the OUI
 
	 8. As root, copy /var/opt/oracle/*tab to the other nodes within the cluster
 
	    After the install is complete, you must copy the emtab and oratab from 
	    /var/opt/oracle to the other nodes within the cluster
 
	    <other node># mkdir -p /var/opt/oracle
	    <other node># rcp <install node>:/var/opt/oracle/*tab /var/opt/oracle
 
         9. Install the 9.0.2.3 Core Patchset
 
	    Complete any pre-requisites before installing the 9.0.2.3 Core Patchset, 
	    refer to the Oracle Metalink Note: 243561.1 for more information.
 
	    When installing the 9.0.2.3 Core Patchset, follow the OUI screens as required. 
	    After installing the software, you will be prompted to execute 
            ${ORACLE_HOME}/root.sh, before the OUI will continue with the configuration
	    assistant.
 
	    Before executing ${ORACLE_HOME}/root.sh perform Step 10.
 
        10. Before executing ${ORACLE_HOME}/root.sh script
 
	    su - <userid>
	    cd  ${ORACLE_HOME}/opmn/conf
	    vi opmn.xml
 
	    Add the following lines to each instanceName,
 
	    <prop name="LD_LIBRARY_PATH" value="${ORACLE_HOME}/lib"/>
	    <prop name="LHOSTNAME" value="<logical host>"/>
	    <prop name="LD_PRELOAD_32" value="libloghost_32.so.1"/>
 
	    You must provide the provide the full path for ${ORACLE_HOME} and the 
	    short name for <logical host>.
 
	    The following shows a sample opmn.xml file after it has been modified,
 
	<ias-instance xmlns="http://www.oracle.com/ias-instance">
	  <notification-server>
	    <port local="6100" remote="6200" request="6003"/>
	    <log-file path="/local/mnt1/ora9ias/opmn/logs/ons.log" level="3"/>
	  </notification-server>
	  <process-manager>
	    <ohs gid="HTTP Server" maxRetry="3">
	      <start-mode mode="ssl"/>
	    </ohs>
	    <oc4j maxRetry="3" instanceName="home" numProcs="1">
	      <config-file path="/local/mnt1/ora9ias/j2ee/home/config/server.xml"/>
	      <oc4j-option value="-properties"/>
	      <port ajp="3000-3100" jms="3201-3300" rmi="3101-3200"/>
	      <environment>
	        <prop name="LD_LIBRARY_PATH" value="/local/mnt1/ora9ias/lib"/>
	        <prop name="LHOSTNAME" value="psemea5"/>
	        <prop name="LD_PRELOAD_32" value="libloghost_32.so.1"/>
	      </environment>
	    </oc4j>
	    <oc4j maxRetry="3" instanceName="OC4J_Demos" gid="OC4J_Demos" numProcs="1">
	      <config-file path="/local/mnt1/ora9ias/j2ee/OC4J_Demos/config/server.xml"/>
	      <java-option value="-Xmx512M "/>
	      <oc4j-option value="-userThreads  -properties"/>
	      <port ajp="3001-3100" jms="3201-3300" rmi="3101-3200"/>
	      <environment>
	        <prop name="%LIB_PATH_ENV%" value="%LIB_PATH_VALUE%"/>
	        <prop name="LD_LIBRARY_PATH" value="/local/mnt1/ora9ias/lib"/>
	        <prop name="LHOSTNAME" value="psemea5"/>
	        <prop name="LD_PRELOAD_32" value="libloghost_32.so.1"/>
	      </environment>
	    </oc4j>
	    <oc4j maxRetry="3" instanceName="OC4J_DAS" gid="OC4J_DAS" numProcs="1">
	      <config-file path="/local/mnt1/ora9ias/j2ee/OC4J_DAS/config/server.xml"/>
	      <java-option value="-server -Xincgc -Xnoclassgc -Xmx256m "/>
	      <oc4j-option value="-properties"/>
	      <port ajp="3001-3100" jms="3201-3300" rmi="3101-3200"/>
	      <environment>
	        <prop name="DISPLAY" value="psemea5:0.0"/>
	        <prop name="LD_LIBRARY_PATH" value="/local/mnt1/ora9ias/lib"/>
	        <prop name="LHOSTNAME" value="psemea5"/>
	        <prop name="LD_PRELOAD_32" value="libloghost_32.so.1"/>
	      </environment>
	    </oc4j>
	    <custom gid="dcm-daemon" numProcs="1" noGidWildcard="true">
	      <start path="/local/mnt1/ora9ias/dcm/bin/dcmctl daemon -logdir /local/mnt1/ora9ias/dcm/logs/daemon_logs"/>
	      <stop path="/local/mnt1/ora9ias/dcm/bin/dcmctl shutdowndaemon"/>
	      <environment>
	        <prop name="LD_LIBRARY_PATH" value="/local/mnt1/ora9ias/lib"/>
	        <prop name="LHOSTNAME" value="psemea5"/>
	        <prop name="LD_PRELOAD_32" value="libloghost_32.so.1"/>
	      </environment>
	    </custom>
	    <log-file path="/local/mnt1/ora9ias/opmn/logs/ipm.log" level="3"/>
	  </process-manager>
	</ias-instance>
 
        11. As root, execute the ${ORACLE_HOME}/root.sh script and continue with the OUI
 
	12. Stop the Oracle Application Server Infrastructure
 
	    After the install is complete, you must stop the infrastructure and place it
	    under the control of the Sun Cluster.
 
	    su - <userid>
 
	    ${ORACLE_HOME}/bin/emctl stop
	    ${ORACLE_HOME}/opmn/bin/opmnctl stopall
	    ${ORACLE_HOME}/bin/oidctl server=oidldapd configset=0 instance=1 stop
 
	    Wait 5-10 seconds for the "oidldapd stop" to be processed by oidmon
 
	    ${ORACLE_HOME}/bin/oidmon stop
	    ${ORACLE_HOME}/bin/lsnrctl stop
	    ${ORACLE_HOME}/bin/sqlplus "/ as sysdba"
	    shutdown
 
	13. Reboot each node in cluster mode
 
	    reboot
 
	14. Continue with Sun Cluster Data Service for Oracle Application Server Guide 
            for Solaris OS, How to Register and Configure Sun Cluster HA for Oracle
            Application Server as a Failover Service

README -- Last modified date:  Monday, March 13, 2006