This OPatch is specifically for EM Cloud Control product only. 
=====FMW based products must not use this.======
This is the README file for OPatch 13.9.3.3.0, the Oracle Interim One-off Patch Installer,
which can be used to upgrade EMCC homes which have OUI version 13.6.0.0.0 or higher.


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

For Enterprise Manager Cloud Control only, 
Make sure OMS is stopped. If not, run the following command to stop the OMS. 
   '<ORACLE_HOME>/bin/emctl stop oms -all' (for linux like platforms) 
   '<ORACLE_HOME>\bin\emctl.bat stop oms -all' (for windows platforms 
   From task manager ensure there are no processes running from the Oracle Home


Installation
----------------------------------
- Backup your <ORACLE_HOME>
 
- Unzip this patch into your staging directory PATCH_HOME
 
- Install the software via:
    java -jar <PATCH_HOME>/6880880/opatch_generic.jar -silent oracle_home=$ORACLE_HOME

- If needed, install the software with custom inventory via:
    java -jar <PATCH_HOME>/6880880/opatch_generic.jar -silent oracle_home=$ORACLE_HOME -invPtrLoc <inventory pointer location>
where inventory pointer location is the absolute path to the oraInst.loc file.

If this Patch is  used by Enterprise Manager customers then please note:

1. Upgrade the OPatch on 13.1 or 13.2 OMS Home :

	export ORACLE_HOME=<EM_MW_HOME>

	$ORACLE_HOME/oracle_common/jdk/bin/java -jar <PATCH_HOME>/6880880/opatch_generic.jar -silent oracle_home=$ORACLE_HOME

	- If needed, install the software with custom inventory via:
	$ORACLE_HOME/oracle_common/jdk/bin/java -jar <PATCH_HOME>/6880880/opatch_generic.jar -silent oracle_home=$ORACLE_HOME -invPtrLoc <inventory pointer location>
where inventory pointer location is the absolute path to the oraInst.loc file.
 
2. Upgrade the OPatch on 13.1 or 13.2 Agent Home :

	export ORACLE_HOME=<AGENT_BASE_DIR>/agent_13.x.0.0.0  , where x = 1 whenupgrading on 13.1 and x=2 when upgrading on 13.2

	$ORACLE_HOME/jdk/bin/java -jar <PATCH_HOME>/6880880/opatch_generic.jar -silent oracle_home=$ORACLE_HOME
 
	- If needed, install the software with custom inventory via:
	$ORACLE_HOME/jdk/bin/java -jar <PATCH_HOME>/6880880/opatch_generic.jar -silent oracle_home=$ORACLE_HOME -invPtrLoc <inventory pointer location>
where inventory pointer location is the absolute path to the oraInst.loc file.

- To validate the installation:
    cd <ORACLE_HOME>/OPatch
    opatch version
    opatch lspatches
 
- Checking if platform requires a 64-bit JVM
Refer Doc ID 2284034.1
If  EM 13c: Upgrading OPatch to 13.9.x in the Enterprise Manager 13c Cloud Control Middleware Home Fails with Error: Unsupported major.minor version 51.0 (Doc ID 2221863.1)

Run the opatch extraction with the -d64 option for <EM 13.2 OMS Oracle Home>/oracle_common/jdk:

$ $JAVA_HOME/bin/java -jar -d64 /<path to the patch download location>/6880880/opatch_generic.jar -silent oracle_home=<EM 13.2 OMS Oracle Home>

After the upgrade of the opatch , Apply the PSU.
 
 
Post-installation Instructions
----------------------------------
 
For Enterprise Manager Cloud Control only:
1) To initialize the configuration, run
omspatcher lspatches
2) Bounce the OMS. Do so on each host for a Multiple OMS.
 
 
Deinstallation
--------------
There is no mechanism to revert only OPatch to an older version.
To revert OPatch, restore the backup for your ORACLE_HOME
 
Documentation and Help
-----------------------
To obtain command names or options from the command prompt, use:
    opatch -help
    opatch napply -help
 
To learn about patching of your specific Oracle Product, go to http://docs.oracle.com and find the install and patching manual for your specific product. To read the OPatch manual, search the web for: "OPatch User's Guide, Release 13".
 
For support articles, search My Oracle Support for "Master Note For OPatch (Doc ID 293369.1)"
 
Verifying the OPatch update in your environment
-----------------------------------------------
Prior to your installing a new OPatch onto your production systems and using it for production patch installation, Oracle recommends you submit the new version of OPatch to the same staged testing process you use for your Oracle patches, such as a new PSU.
 
If you run into issues triggered by the new OPatch (rare), you must restore the Oracle home to revert OPatch. Any application of a patch using the new version of OPatch renders the home incompatible with prior versions of OPatch. If you cannot restore the Oracle home, due to the backup containing very old configuration or log files, contact Oracle support.
 
Tip: The opatch prereq commands and opatch with the -report option do not render the home incompatible with the prior OPatch version because they do not update the patch database in the Oracle Home. You may wish to exploit this to do non-destructive patch and OPatch update testing.
 
Notes
-----
OPatch historically used unzip to install files in the home. For versions greater than or equal to 13.6, it now uses the OUI installation tooling. This ensures that installer both executes the file updates and logs the components and file changes to the OUI meta-data. A pure unzip install means the OUI tooling is not aware of these changes, which has on rare occasions led to upgrade related issues.

