===============================
Interim Patch for Bug: 17533212
===============================

Date: Oct 28, 2013
---------------------------------
Platform Patch for   : Linux x86-64
Product Patched      : Oracle Fusion Middleware High Availability
Product Version      : 12.1.2.0.0

This document describes how to install the interim patch for
bug # 17533212. It includes the following sections: 

	Section 1, "Prerequisites"

	Section 2, "Pre-Installation Instructions"

	Section 3, "Installation Instructions"

	Section 4, "Post-Installation Instructions"

	Section 5, "Deinstallation Instructions"

	Section 6, "Post Deinstallation Instructions" 

	Section 7, "Bugs Fixed by This Patch" 
	

1 Prerequisites
----------------

Ensure that you meet the following requirements before you install or
deinstall the patch:
	
1. Before applying the non-mandatory patches, ensure that you have the
   exact symptoms described in the bug.

2. Review and download the latest version of OPatch 13.1.x via patch 6880880.
  (OPatch version 13.1.0.0.0 or higher)

   Patch :p6880880_131000_Generic.zip

  a. Oracle recommends that all customers be on the latest version of OPatch.
     Review the My Oracle Support note 1587524.1 and follow the instructions
     to update to the latest version if needed. Click the following link to
     view the note:

     Doc ID 1587524.1 - Using OPatch 13.1 for Oracle Fusion Middleware 12c (12.1.2+)
     https://support.oracle.com/rs?type=doc&id=1587524.1

  b. For FMW Opatch usage, refer to the document at:
     http://www.oracle.com/pls/topic/lookup?ctx=fmw121x00&id=OPATC
     
3. Verify the OUI Inventory.
   OPatch needs access to a valid OUI inventory to apply patches. 
   
   Note: This needs the ORACLE_HOME to be set(refer section "2. Pre-Installation Instructions") 
   prior to run the below commands:
   
   Validate the OUI inventory with the following commands:

   $ opatch lsinventory  

   If the command errors out, contact Oracle Support and work to validate
   and verify the inventory setup before proceeding.

4. Confirm the executables appear in your system PATH.

   The patching process will use the unzip and the OPatch executables. After
   setting the ORACLE_HOME environment, confirm if the following executables
   exist, before proceeding to the next step:

	- which opatch
	- which unzip

   If either of these executables do not show in the PATH, correct the
   problem before proceeding.

5. Create a location for storing the unzipped patch. This location
   will be referred to later in the document as PATCH_TOP.

   NOTE: On WINDOWS, the prefrred location is the drive root directory. 
   For example, "C:\PATCH_TOP" and avoid choosing locations like, 
   "C:\Documents and Settings\username\PATCH_TOP". 
   This is necessary due to the 256 characters limitation on windows     
   platform.
   

2 Pre-Installation Instructions
-------------------------------

a. Set the ORACLE_HOME environment variable to the directory where you have installed Oracle HTTP Server (OHS).
   for example: export ORACLE_HOME=/tmp/1212mwhome
 
b. Stop all Oracle HTTP Server Instances.
   for example: 
   $ stopComponent.sh ohs1

If the owner of hasbind is the root user, The next steps must be performed as the root user. 
If you do not have root access, have the system administrator perform these steps.

c. Change ownership of the file to the user using which OHS was insatlled:
   chown <user> $ORACLE_HOME/oracle_common/bin/hasbind
   
d. Change the permissions on the file as follows:
   chmod 755 $ORACLE_HOME/oracle_common/bin/hasbind

      
3 Installation Instructions
---------------------------

Note: If you are using a 64-bit install, then 64-bit jdk only should be used throughout. 
      This should include both shiphome install and patch application. Although you can 
      use 32-bit jdk on 64-bit boxes, but since 64-bit is the primary platform, you must 
      use 64-bit jdks for all such installations.  
      
      OPatch commands should be run with -jre option as :

 e.g. opatch apply -jre $ORACLE_HOME/jdk/jre
        or
       opatch rollback -id <patch_id> -jre $ORACLE_HOME/jdk/jre 


1. Unzip the patch zip file into the PATCH_TOP.

   $ unzip -d PATCH_TOP p17533212_121200_Linux-x86-64.zip
   
     NOTE: In WINDOWS, the unzip command might not work as this zip has 
     certain contents which passes the 256 characters limit. 
     To overcome this problem, please use alternate ZIP utility like 
     7-Zip to unzip the patch. 
     
     For example: To unzip using 7-zip, run the command: 
       "c:\Program Files\7-Zip\7z.exe" x p17533212_121200_Linux-x86-64.zip
   
2. Set your current directory to the directory where the patch is located.

   $ cd PATCH_TOP/17533212

3. Run OPatch to apply the patch.

   $ opatch apply
       
When OPatch starts, it validates the patch and makes sure that there are no
conflicts with the software already installed in the ORACLE_HOME.
  OPatch categorizes two types of conflicts:

     a. Conflicts with a patch already applied to the ORACLE_HOME
        In this case, stop the patch installation, and contact Oracle Support
        Services.

     b. Conflicts with subset patch already applied to the ORACLE_HOME
        In this case, continue the install, as the new patch contains all the
        fixes from the existing patch in the ORACLE_HOME.


4 Post-Installation Instructions
---------------------------------
The next steps must be performed as the root user. 
If you do not have root access, have the system administrator perform these steps.

a. i) Change ownership of the file to root:
      chown root $ORACLE_HOME/oracle_common/bin/hasbind
   
   ii) Change the permissions on the file as follows:
      chmod 4755 $ORACLE_HOME/oracle_common/bin/hasbind

b. Start all Oracle HTTP Server Instances.
   for example: 
   $ startComponent.sh ohs1

5 Deinstallation Instructions
------------------------------

If you experience any problems after installing this patch, remove the patch as
follows:

1. Make sure to follow the same Prerequisites or pre-install steps (if any)
   when deinstalling a patch.  
   This includes setting up any environment variables like ORACLE_HOME and
   verifying the OUI inventory before deinstalling.
   
   a) Change ownership of the file to the user using which OHS was insatlled:
      chown <user> $ORACLE_HOME/oracle_common/bin/hasbind
   
   b) Change the permissions on the file as follows:
      chmod 755 $ORACLE_HOME/oracle_common/bin/hasbind

2. Change to the directory where the patch was unzipped.

   $ cd PATCH_TOP/17533212

3. Run OPatch to deinstall the patch.

   $ opatch rollback -id 17533212
                          

6 Post Deinstallation Instructions
-----------------------------------
a. Restart all Oracle HTTP Server Instances.
   for example: 
   $ startComponent.sh ohs1

7 Bugs Fixed by This Patch
--------------------------

17533212 - OHS CAN NOT STARTUP WITH PRIVILEGE PORT ON LINUX 6  

-----------------------------------------------------------------------------
DISCLAIMER:

This interim patch has only undergone basic unit testing, and has not been
through a complete test cycle generally followed for a production patch set. 
Though the fixes in this document rectifies the bug, Oracle Corporation will
not be responsible for other issues that may arise due to these fixes. 
Oracle Corporation recommends to later upgrade to the next production patch
set, when available. Applying this patch could overwrite other interim
patches applied since the last patch set. Customers need to make a request
to Oracle Support for a patch that includes those fixes, as well as inform
Oracle Support about all the patches installed when a Service Request is
opened. Please download, test, and provide feedback as soon as possible
to assist in the timely resolution of this problem.

Copyright (c) 2013, Oracle and/or its affiliates. All rights reserved.
-----------------------------------------------------------------------------