Below is method to apply weblogic patches on Oracle EBS system
Let me explain. For example,
fs1 is Run FS & fs2 is Patch FS
Follow below:
1) source /erp_appl/apps/EBSapps.env run
adop phase=prepare
2) source /erp_appl/apps/EBSapps.env patch
Apply all the WLS Patches using bsu.sh on fs2 (Patch FS)
Installing a patch
cd $FMW_HOME/utils/bsu
./bsu.sh -install -patch_download_dir=$FMW_HOME/utils/bsu/cache_dir -patchlist=<patch_name without jar extension> -prod_dir=$FMW_HOME/wlserver_10.3 -log=patch_apply.log
Removing a patch
cd $FMW_HOME/utils/bsu
./bsu.sh -remove -patchlist=<patch_name without jar extension> -prod_dir=$FMW_HOME/wlserver_10.3
List the patches applied
cd $FMW_HOME/utils/bsu
./bsu.sh -report -bea_home=$FMW_HOME -output_file=bsu_patch_report.log
3) source /erp_appl/apps/EBSapps.env run
adop phase=finalize
adop phase=cutover
adop phase=cleanup
4) source /erp_appl/apps/EBSapps.env run
adop phase=fs_clone
Examples
------------
Oracle
Weblogic PSU Patching Process
1.
Introduction:
Read
out all important oracle patching related documents and verify whether it
applies for our database version or not.
2.
Backup of Database/Application
& Weblogic home.
Before
applying any patches in database, kindly take a backup as follows.
- Full database
- Full Application
- Weblogic home
3.
Download Weblogic CPU patches
from ORACLE site
-
unzip p29633432_1036_Generic.zip to {MW_HOME}/utils/bsu/cache_dir.
source
/erp_appl/apps/EBSapps.env run and adop phase=prepare
-
source
/erp_appl/apps/EBSapps.env patch and apply patch (p29633432_1036_Generic.zip)
on patch file system with bsu.sh command
-
Command:
./bsu.sh
-install -patch_download_dir=/erp_appl/apps/fs2/FMW_Home/utils/bsu/cache_dir
-patchlist=MXLE -prod_dir=/erp_appl/apps/fs2/FMW_Home/wlserver_10.3
-
-
The
above patch will have following 5 conflict patches, hence remove conflict
patches first and proceed with main patch.
Remove conflicts:
1] bash-4.4$ ./bsu.sh
-prod_dir=/erp_appl/apps/fs2/FMW_Home/wlserver_10.3 -patchlist=PSVV -verbose
-remove ------> Removed without any
conflicts
2] bash-4.4$ ./bsu.sh
-prod_dir=/erp_appl/apps/fs2/FMW_Home/wlserver_10.3 -patchlist=7P2C -verbose
-remove ------> Removed without any
conflicts
3] bash-4.4$ ./bsu.sh
-prod_dir=/erp_appl/apps/fs2/FMW_Home/wlserver_10.3 -patchlist=45ET -verbose
-remove ------> Removed without any
conflicts
4] bash-4.4$ ./bsu.sh
-prod_dir=/erp_appl/apps/fs2/FMW_Home/wlserver_10.3 -patchlist=96N5 -verbose -remove ------> Removed without any conflicts
5] bash-4.4$ ./bsu.sh
-prod_dir=/erp_appl/apps/fs2/FMW_Home/wlserver_10.3 -patchlist=FMJJ -verbose -remove ------> Removed ( It has conflicts:
7P2C,96N5 , so removed
in step2,4)
Apply main patch:
./bsu.sh
-install -patch_download_dir=/erp_appl/apps/fs2/FMW_Home/utils/bsu/cache_dir
-patchlist=MXLE -prod_dir=/erp_appl/apps/fs2/FMW_Home/wlserver_10.3
-
source
/erp_appl/apps/EBSapps.env run and adop phase=cutover
-
source
/erp_appl/apps/EBSapps.env run and adop phase=cleanup
4. Perform Sanity
Test
Post
successful patching, perform basic sanity test and release it to end users if
everything is fine and as expected
5.
Run FS_CLONE
source /erp_appl/apps/EBSapps.env run and adop phase=fs_clone
Wonderfully explained to apply patch using R12.2 adop steps
ReplyDelete