R12 PATCHING TECHNOLOGY COMPONENTS

Oracle E-Business Suite 12.2 Patching Technology Components Guide

 (Doc ID 1355068.1)

• Oracle E-Business Suite Release 12.2 utilizes multiple technology components.
• Each component has its own Oracle Home, which can be patched individually.

Article describes the technology patching tools and how are they used in EBS R12 (Release 12.2)

Patching Oracle E-Business Suite Release 12.2 Technology Components

Oracle Homes

Oracle E-Business Suite Release 12.2 uses the following Oracle Homes:

·         Oracle Fusion Middleware

• Oracle WebLogic Server (WLS) 10.3.6
• OHS (WebTier) 11.1.1 and Oracle Common (Common Modules)

·         Application Server (OracleAS)

• Forms and Reports 10.1.2

·         Oracle Database

• Oracle Database Server 11.2 or 12.0

Note: Oracle E-Business Suite Release 12.2 uses multiple Oracle Homes to accommodate the various technology components. When applying a patch, you must ensure the environment is set to point to the correct Oracle Home.

Application EBS Technology Patching Cycle: Fusion Middleware

Application tier technology patches are applied to the patch file system using a native patching tool such as OPatch or SmartUpdate, and the changes are then propagated to the run file system as part of an Online Patching cycle

The following is an overview of the process to follow when applying a technology patch within Oracle E-Business Suite**.

Note: EBS_ROOT is the base directory of your Oracle E-Business Suite Release 12.2 installation.

1. Download any required technology patches and unzip them into the $NE_BASE/EBSapps/patch directory.
2. Prepare the system for patching:

$ source <EBS_ROOT>/EBSapps.env3 run
$ adop phase=prepare

3. Prepare to apply technology patches to the Oracle Home on the patch file system:

$ source <EBS_ROOT>/EBSapps.env3 patch

Refer to Table 1 below for details about applying technology patches application on the application tier.

4. Optionally, apply any Oracle E-Business Suite patches planned for this patching cycle:

$ adop phase=apply patches=<patch_list>

5. After all patches have been successfully applied, complete the patching cycle:

$ adop phase=finalize
$ adop phase=cutover
$ source <EBS_ROOT>EBSapps.env3 run
$ adop phase=cleanup

6. Synchronize the technology level between patch and run file systems:

$ adop phase=fs_clone

Note: The above overview does not apply if patches are being applied in hotpatch or downtime mode, where technology patches are applied directly to the run file system outside an online patching cycle. If you are installing or upgrading to Release 12.2, you may have been referred to this document from My Oracle Support Knowledge Document 1617461.1 Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2. If you are following Path A of that document, note that it uses hot patching, so you will not use the patching cycle shown above until later in the installation or upgrade process.

Table 1 - Fusion Middleware Oracle Home

Oracle Home	Patch Installation Instructions	Inventory Command for Patch Installation Verification	Patch De-installation Instructions	Notes
WebLogic Server	Review the patch Readme Follow the Readme instructions, for example by running the commands: $ cd $FMW_HOME/utils/bsu $ bsu.sh3 -prod_dir=<path>/FMW_Home/wlserver_10.3 -patchlist=<patchID1> -verbose -install	Run the commands: $ cd $FMW_HOME/utils/bsu $ bsu.sh3 -report -bea_home=<pathto>/FMW_Home -output_format=text	Follow the patch Readme instructions, for example by running the command: $ ./bsu.sh3 -remove -patchlist=<patchID1> -prod_dir=<path>/FMW_Home/wlserver_10.3 -verbose	Oracle Smart Update Applying Patches to Oracle WebLogic Server Chapter 8: Using the Command-Line Interface More information on how to apply WebLogic Server (WLS) patches using smart update is available in My Oracle Support Knowledge Document 876004.1. More information on how to locate and download patches for WebLogic is available in My Oracle Support Knowledge Document 1302053.1.
Web Tier and Utilities (OHS)	Review the patch Readme Set ORACLE_HOME to the required FMW Oracle Home.2 Include $ORACLE_HOME/OPatch in the PATH Change directory to the patch directory Follow the Readme instructions, for example by running the command: $ opatch apply	Set ORACLE_HOME to the required FMW Oracle Home.2 For example: $ export ORACLE_HOME = $IAS_ORACLE_HOME Include $ORACLE_HOME/OPatch in the PATH Run the command: $ opatch lsinventory	Follow the Readme instructions, for example by running the command: $ opatch rollback -id <patchnumber>	More information on OPatch is available in My Oracle Support Knowledge Document 293369.1.
Oracle Fusion Middleware Common	Review the patch Readme Set ORACLE_HOME to the required FMW Oracle Home.2 Include $ORACLE_HOME/OPatch in the PATH Change directory to the patch directory Follow the Readme instructions, for example by running the command: $ opatch apply	Set ORACLE_HOME to the required FMW Oracle Home.2 For example: $ export ORACLE_HOME = $FMW_HOME/oracle_common Include $ORACLE_HOME/OPatch in the PATH. Run the command: $ opatch lsinventory	Follow the Readme instructions, for example by running the command: $ opatch rollback -id <patchnumber>	More information on OPatch is available in My Oracle Support Knowledge Document 293369.1.
Forms and Reports 10.1.2	Review the patch Readme Source the Application Server Oracle Home Environment Include $ORACLE_HOME/OPatch in the PATH Change directory to the patch directory Follow the Readme instructions, for example by running the command: $ opatch apply	Source the OracleAS Oracle Home environment. Include $ORACLE_HOME/OPatch in the PATH. Run the command: $ opatch lsinventory	Follow the Readme instructions, for example by running the command: $ opatch rollback -id <patchnumber>	More information on OPatch is available in My Oracle Support Knowledge Document 293369.1. Additional actions specific to E-Business Suite may be necessary after patch install or rollback. Refer to My Oracle Support Knowledge:Document 437878.1 Steps 4.1 and 4.2.

¹ PatchID is a combination of letters and numbers. As a general rule the PatchID is the name of the jar file without the .jar extension.
² SetOracleCommon.env and SetWebtier.env are provided within the $FMW_HOME directory scripts that set the Oracle Home for patching purposes.
³ On Windows, command (.cmd) scripts such EBSapps.cmd and bsu.cmd are the equivalent of the shell scripts mentioned for UNIX platforms.

Note: You may verify the installation of any WebLogic Patch by examing the inventory output from:

$ cd $FMW_HOME/utils/bsu
$ bsu.sh -report

 

Database Oracle Home

The Database Oracle Home is not a part of the the online patching process within Oracle E-Business Suite 12.2. We strongly recommend applying required database patches as soon as possible, or you may experience issues.

If you plan to combine applying the required database patches as part of your next online patching cycle, you can apply them after the cutover phase of that cycle:

On application tier primary node:

$source <INSTALL_BASE>/EBSapps.env4 run

$ adop phase=prepare
$ adop phase=apply patches=1111,2222
$ adop phase=finalize
$ adop phase=cutover mt_restart=no

On database node:

$ source <INSTALL_BASE>/<sid_machine>.env
$ $ORACLE_HOME/appsutil/scripts/<sid_machine>/addbctl.sh stop
$ $ORACLE_HOME/OPatch/opatch apply <Database Patch >
$ $ORACLE_HOME/appsutil/scripts/<sid_machine>/addbctl.sh start

On application tier primary node:

$ source <INSTALL_BASE>/EBSapps.env4 run
$ adstrtal.sh -mode=allnodes
$ adop phase=cleanup

Table 2 - Database Oracle Home

Oracle Home	Patch Installation Instructions	Inventory Command for Patch Installation Verification	Patch De-installation Instructions	Notes
Database (RDBMS)	Review the patch Readme Source the Database Oracle Home environment Include $ORACLE_HOME/OPatch in the PATH Change directory to the patch directory Follow the Readme instructions, for example by running the command: $ opatch apply	Source the Database Oracle Home environment Include $ORACLE_HOME/OPatch in the PATH Run the command: $ opatch lsinventory	Follow the Readme instructions, for example by running the command: $ opatch rollback -id <patchnumber>	More information on OPatch is available in My Oracle Support Knowledge Document 293369.1.