We already know the general practice to apply application patches to R12.2 through online patching
Adop(Ad online patching utility) explained R12.2
R12.2 Online patching cycle Summary
Let’s explore the steps on how to apply database patches , weblogic patches , 10.1.2 patches , web-tier patches to the R12.2 tech stack.
We can apply the same online patching cycle for the below technology patches
a. Weblogic patches
b. Web-tier patches
c. Oracle home 10.1.2 patches
d. Oracle_common patches
Database patches cannot be applied through online patching cycle as they require downtime
The General steps for Technology patches are
1.Download any required technology patches and unzip them into the $NE_BASE/EBSapps/patch directory.
- Prepare the system for patching:
$ source <EBS_ROOT>/EBSapps.env $ adop phase=prepare
- Apply the technology patches on the patch filesystem
Prepare to apply technology patch to the Oracle Home on the patch file system:
$ source <EBS_ROOT>/EBSapps.env patch
Now apply the technology patches to the patch filesystem as given in below sections
Optionally, apply any Oracle E-Business Suite patches planned for this patching cycle
$ adop phase=apply patches=<patch_list>
4.After all patches have been successfully applied, complete the patching cycle:
$ adop phase=finalize $ adop phase=cutover
- Clean up phase
$ source <EBS_ROOT>EBSapps.env run $ adop phase=cleanup
Synchronize the technology level between patch and run file systems:
$ adop phase=fs_clone
So it is pretty same as other patches.Now in next block ,I will explain how to apply patches to the tech stack components
How to apply patch to Weblogic in R12.2
Patch Installation
$ cd $FMW_HOME/utils/bsu $ bsu.sh -prod_dir=<path>/FMW_Home/wlserver_10.3 -patchlist=<patchID1> -verbose -install
Patch report
$ cd $FMW_HOME/utils/bsu $ bsu.sh -report -bea_home=<pathto>/FMW_Home -output_format=text
Patch de-installation
Follow the patch Readme instructions, for example by running the command:
$ ./bsu.sh -remove -patchlist=<patchID1> -prod_dir=<path>/FMW_Home/wlserver_10.3 -verbose
How to fix the “GC overhead limit” or “Java heap space” error while applying weblogic patches
When using the bsu.sh script to install an Oracle WebLogic Server patch, you may receive an out of memory error for either “GC overhead limit” or “Java heap space”. In such a case, run the commands shown below (the examples are for UNIX).
Source the Oracle E-Business Suite Release 12.2 environment.
Change directory to $FMW_HOME/utils/bsu.
Back up the existing copy of bsu.sh (or bsu.cmd on Microsoft Windows):
$ cp bsu.sh bsu.sh_backup
Open bsu.sh in a text editor such as vi and change the line:
MEM_ARGS="-Xms256m -Xmx512m to: MEM_ARGS="-Xms512m -Xmx2048m -XX:+UseParallelGC"
Save the modified bsu.sh file and exit the editor.
How to apply patches to Web Tier and Utilities (OHS)
Patch Installation
$cd $FMW_HOME $. ./SetWebtier.env $PATH=PATH:$ORACLE_HOME/OPatch $ cd <patch dir> $ opatch apply
How to check for patch
$cd $FMW_HOME $. ./SetWebtier.env $PATH=PATH:$ORACLE_HOME/OPatch $ opatch lsinventory
How to rollback the patch
$cd $FMW_HOME $. ./SetWebtier.env $PATH=PATH:$ORACLE_HOME/OPatch $ opatch rollback -id <patchnumber>
How to apply patches to Oracle Fusion Middleware Common
Patch installation
$cd $FMW_HOME $. ./ SetOracleCommon.env $ PATH=PATH:$ORACLE_HOME/OPatch $cd <patch dir> $ opatch apply
How to check for patch
$cd $FMW_HOME $. ./ SetOracleCommon.env $ PATH=PATH:$ORACLE_HOME/OPatch $ opatch lsinventory
How to rollback the patch
$cd $FMW_HOME $. ./SetOracleCommon.env $ PATH=PATH:$ORACLE_HOME/OPatch $ opatch rollback -id <patchnumber>
How to apply patches to Forms and Reports 10.1.2
Patch installation
$Source the Environment $ PATH=PATH:$ORACLE_HOME/OPatch $ cd <patch dir> $ opatch apply
How to check for patch
$Source the Environment
$ PATH=PATH:$ORACLE_HOME/OPatch $ opatch lsinventory
How to rollback the patch
Source the Environment
$ PATH=PATH:$ORACLE_HOME/OPatch $ opatch rollback -id <patchnumber>
How to apply patches to Database Oracle Home in R12.2
The Database Oracle Home is not a part of the the online patching process within Oracle E-Business Suite 12.2.
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. This will increase the cutover time but database patches usually takes less time.
Steps in that case would be
On application tier primary node:
$source <INSTALL_BASE>/EBSapps.env run $ adop phase=prepare $ adop phase=apply patches=<patch list> $ 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.env run $ adstrtal.sh -mode=allnodes $ adop phase=cleanup
If you have Oracle RAC environment, you can apply the database patches without any downtime also using rollover patching method,where you bring the instance one by one and apply the patches
