Oracle Database 11g Release 11.2.0.4.0
ORACLE JAVA TECHNOLOGY Patch for Bug# 19852360 for Generic Platforms

(RAC Rolling Installable)
Released: Fri Oct 24 00:15:19 PDT 2014
   
This document describes how you can install the one-off patch for bug#  19852360 on your Oracle Database 11g Release 11.2.0.4.0
This patch includes security vulnerability for CVE-2014-4289 & CVE-2014-6544 and is applicable to Server Home, Grid Infrastructure home, Client-Only installations and Instant Client Installations.

(The Instant Client installation is not the same as the client-only Installation. For additional information about Instant Client installations, 
see Oracle Call Interface Programmer's Guide : http://docs.oracle.com/cd/E11882_01/appdev.112/e10646/oci01int.htm#LNOCI019 )

(I) Prerequisites
--------------------
Before you install or deinstall the patch, ensure that you meet the following requirements:

Note: In case of an Oracle RAC environment, meet these prerequisites on each of the nodes.

1.	Ensure that the Oracle Database on which you are installing the patch or from which you are rolling back the patch is Oracle Database 11g Release 11.2.0.4.0.

2.      Oracle recommends you to use the latest version of OPatch. 
	If you do not have the latest version, then follow the instructions outlined in the My Oracle Support note 224346.1 available at:
	https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=224346.1 
	
3.	Ensure that you set (as the home user) the ORACLE_HOME environment variable to the Oracle home.

4.	Ensure that the $PATH definition has the following executables: make, ar, ld and nm. The location of these executables depends on your operating system. On many operating systems, they are located in /usr/ccs/bin.

5.	Ensure that you verify the Oracle Inventory because OPatch accesses it to install the patches. To verify the inventory, run the following command.
	$ opatch lsinventory 
	
	Note:
	-	If this command succeeds, it will list the Top-Level Oracle Products and one-off patches if any that are installed in the Oralce Home.
			- Save the output so you have the status prior to the patch apply.
	-	If the command displays some errors, then contact Oracle Support and resolve the issue first before proceeding further.

6.	(Only for Installation) Maintain a location for storing the contents of the patch ZIP file. In the rest of the document, this location (absolute path) is referred to as <PATCH_TOP_DIR>. Extract the contents of the patch ZIP file to the location (PATCH_TOP_DIR) you have created above. To do so, run the following command:
	$ unzip -d <PATCH_TOP_DIR> p19852360_112040_Generic.zip

7.	(Only for Installation) Determine whether any currently installed interim patches conflict with this patch 19852360 as shown below:
	$ cd <PATCH_TOP_DIR>/19852360
	$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./
	
	The report will indicate the patches that conflict with this patch and the patches for which the current 19852360 is a superset.
	
	Note:
	When OPatch starts, it validates the patch and ensures that there are no conflicts with the software already installed in the ORACLE_HOME. OPatch categorizes conflicts into the following types: 
	-	Conflicts with a patch already applied to the ORACLE_HOME that is a subset of the patch you are trying to apply  - In this case, continue with the patch installation because the new patch contains all the fixes from the existing patch in the ORACLE_HOME. The subset patch will automatically be rolled back prior to the installation of the new patch.
	-	Conflicts with a patch already applied to the ORACLE_HOME - In this case, stop the patch installation and contact Oracle Support Services.
	
8.	For RAC environment, Ensure that you shut down all the services(database, ASM, listeners, nodeapps, and CRS daemons) running from the Oracle home of Oracle Database home.

	-	Stopping services from Database home in Clustered Environments (Run as the database home owner)
		$ $ORACLE_HOME/bin/srvctl stop instance -d <db_unique_name> -n <node_name>

	-	Stopping services from Database home in Standalone Servers or Non-Clustered Environments (Run as the database home owner)
		$ $ORACLE_HOME/bin/srvctl stop home -o <ORACLE_HOME> -s <STAT_FILE_LOCATION>
	
	<STAT_FILE_LOCATION> is a path to save the state of the database configuration temporarily. The previous command will stop the HA-managed clusterware resource for the specified database 
	home, and create a state file that can be used when restarting the same. Repeat the same command for all other database homes if you have more than one on the node, and make sure you 
	use different <STAT_FILE_LOCATION> each time.

	Note:
	-	For a RAC environment, stop all services on a node, after you patch this node, start the services on this node. Repeat this process for each of the other nodes of the Oracle RAC system. OPatch is used on only one node at a time.
	-	If the Oracle Database you are patching was installed with an operating system user account that is different from the user account used for installing the Oracle ASM, then run srvctl as the 	
		database home user (RDBMS home user) to stop the database instance on each node:
		$ $ORACLE_HOME/bin/srvctl stop instance -d <db_unique_name> -n <node_name>		
		
	For a Non-RAC environment, shut down any services or programs using JDBC (eg: dbcontrol services). Shutting down database, listeners and other services associated with the Oracle home are not required.

9.	Run the pre-root script as a root user from the Oracle home of Oracle Grid Infrastructure:

	-	Running the script for Grid Infrastructure home in Clustered Environments (Run as root)
		# $ORACLE_HOME/crs/install/rootcrs.pl -unlock 

	-	Running the script for Grid Infrastructure home on Standalone Servers or Non-Clustered Environments (Run as root)
		# $ORACLE_HOME/crs/install/roothas.pl -unlock 	

	Note: If you are applying this patch to a Database home, then skip this step.

(II) Installation
-----------------
To install the patch, follow these steps:

1.	Set your current directory to the directory where the patch is located and then run the OPatch utility from the Oracle home for which you are applying the patch to either Oracle Grid Infrastructure or Oracle Database home:

	$ cd <PATCH_TOP_DIR>/19852360

	$ opatch apply
	
2.	Verify whether the patch has been successfully installed by running the following command:

	$ opatch lsinventory

3.	Run the post script as a root user from the Oracle home of Oracle Grid Infrastructure:

	-	Running the script for Grid Infrastructure home in Clustered Environments (Run as root)
		# $ORACLE_HOME/crs/install/rootcrs.pl -patch 

	-	Running the script for Grid Infrastructure home on Standalone Servers or Non-Clustered Environments (Run as root)
		# $ORACLE_HOME/crs/install/roothas.pl -patch 

	Note: If you are applying this patch to a Database home, then skip this step.

6.	Restart all the services from the Oracle home.

	-	Restarting services from Database home in Clustered Environments (Run as the database home owner)
		$ $ORACLE_HOME/bin/srvctl start instance -d <db_unique_name> -n <node_name>

	-	Restarting services from Database home on Standalone Servers or Non-Clustered Environments (Run as the database home owner)
		$ $ORACLE_HOME/bin/srvctl start home -o <ORACLE_HOME> -s <STAT_FILE_LOCATION>
	
	<STAT_FILE_LOCATION> refers to the absolute path leading up to the file name of the STAT_FILE that was created when you stopped the services.

	Note:
	-	If you applied this patch to a database home, then start the services from the Oracle home of the database in the usual way. You do not have to use the srvctl command in that case.
	-	If the Oracle Database was installed with an operating system user account that is different from the user account used for installing the Oracle ASM, then run srvctl as the database home user 
	(RDBMS home user) to start the database instance on each node:
	$ $ORACLE_HOME>/bin/srvctl start instance -d <db_unique_name> -n <node_name>



(III) Deinstallation
--------------------
Ensure to follow the Prerequsites (Section I). To deinstall the patch, follow these steps:

1.	Deinstall the patch by running the following command from the Oracle home for which you are deinstalling the patch to either Oracle Grid Infrastructure or Oracle Database home::
	
	$ opatch rollback -id 19852360

2.	Run the post script as a root user from the Oracle home of Oracle Grid Infrastructure:

	-	Running the script for Grid Infrastructure home in Clustered Environments (Run as root)
		# $ORACLE_HOME/crs/install/rootcrs.pl -patch 

	-	Running the script for Grid Infrastructure home on Standalone Servers or Non-Clustered Environments (Run as root)
		# $ORACLE_HOME/crs/install/roothas.pl -patch 

	Note: If you are rolling back the patch from a Database home, then skip this step.

3.	Restart all the services from the Oracle home.

	-	Restarting services from Database home in Clustered Environments (Run as the database home owner)
		$ $ORACLE_HOME/bin/srvctl start instance -d <db_unique_name> -n <node_name>

	-	Restarting services from Database home in Standalone Servers or Non-Clustered Environments (Run as the database home owner)
		$ $ORACLE_HOME/bin/srvctl start home -o <ORACLE_HOME> -s <STAT_FILE_LOCATION>
	
	<STAT_FILE_LOCATION> refers to the absolute path leading up to the file name of the STAT_FILE that was created when you stopped the services.

	Note:
	-	If you rolled back the patch to a database home, then start the services from the Oracle home of the database in the usual way. You do not have to use the srvctl command in that case.
	-	If the Oracle Database was installed with an operating system user account that is different from the user account used for installing the Oracle ASM, then run srvctl as the database home user 
	(RDBMS home user) to start the database instance on each node:
	$ $ORACLE_HOME>/bin/srvctl start instance -d <db_unique_name> -n <node_name>


4.	Ensure that you verify the Oracle Inventory and compare the output with the one run before the patch installation and re-apply any patches that were rolled back as part of this patch apply. To verify the inventory, run the following command:

	$ opatch lsinventory



(IV) Bugs Fixed by This Patch
---------------------------------
The following are the bugs fixed by this patch:
  19852360: ORACLE JAVAVM COMPONENT 11.2.0.4.1 DATABASE PSU - GENERIC JDBC PATCH (OCT2014)

--------------------------------------------------------------------------
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
--------------------------------------------------------------------------