Recently, I had a chance to apply some patches to Fusion Applications environment. I must admit that the patching itself is a bit different here from what we have been used to in E-Business Suite Applications and seems to be more advanced and user friendly which is a good thing. First of all, we have now a choice of three different tools for specific patching requirements:
- Oracle Fusion Applications Patch Manager (fapmgr)
- Oracle Fusion Applications Release Update Patch Installer
- Oracle Fusion Applications Language Pack Installer
All three names are self explanatory, but compared to eBS where we would be using one tool for any patching (adpatch) – it is distinguished in Fusion Apps. In this blog post, I will be describing the option 1 only on the real world example case. As you have probably guessed already, the Fusion Applications Patch Manager is used for applying standard and one-off patches. The patch manager itself consists from two already known (for years) tools: OPatch for the Oracle Fusion Middleware artifacts and Oracle Fusion Applications AutoPatch for artifacts associated with the database. Depending on what needs to be patched or what is inside in the corresponding patch, FA patch manager will automatically choose which tool to assign the patching or coordinate the activities if both components are to be patched. There are lots of options which can be passed to patching manager, all of them can be find in standard Oracle documentation here, however, I would review only couple of them, which are the most useful and interesting to my mind.
One of the things I like most is that patching manager can produce readable reports based on different options which I believe will be very helpful during Fusion Apps administration. There are such options available as Patch impact which would display system areas affected, prerequisites, bug fixes included, etc. Didn’t you miss this in eBS adpatch? Another great report available is for the applied patches and installed family products. In eBS I would be using patchsets.sh script for the same. Now it is bundled all in one place. Let’s see how the impact report looks like.
[oracle@fusionapps]$ cd /fa_home/apps_home/fusionapps/applications/lcm/ad/bin [oracle@fusionapps bin]$ ./fapmgr.sh report -patchimpact -patchtop /fa_home/patches Oracle Fusion Applications Patch Manager Version 11.1.4.0.0 Copyright (c) 2012 Oracle Corporation. All rights reserved. Archiving existing log files from [/fa_home/apps_home/fusionapps/applications/admin/FUSION/log] to [/fa_home/apps_home/fusionapps/applications/admin/FUSION/logarchive/REPORT-PATCHIMPACT/20130104111936]. Started validating the Database connection. Completed validating the Database connection. Started running apply pre-reqs. Please monitor OPatch log file: /fa_home/apps_home/fusionapps/applications/cfgtoollogs/opatch/14050318_Jan_04_2013_11_21_56/ ApplyPrereq2013-01-04_11-21-56AM_1.log All apply pre-reqs for middleware artifacts have passed. Patch Impact Report Patch Number: 14050318 Fusion Applications Oracle Home: /fa_home/apps_home/fusionapps/applications Language: US Platform: Generic Bug Fixes -------------------------------------------------------------------------------- BUG NO. | BUG DESCRIPTION | Exists in | | Oracle Home -------------------------------------------------------------------------------- 14050318 | DISABLE QTP FOR RUP3 FRESH INSTALL AND UPGRADE | No | CUSTOMERS | -------------------------------------------------------------------------------- Fusion Applications Prerequisite Bug Fixes -------------------------------------------------------------------------------- BUG NO. | BUG DESCRIPTION -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- Prerequisite Bug Fixes Not in FA_ORACLE_HOME: No prerequisite bug fixes missing for patch #14050318 Prerequisites on other products: Although Patch Manager does not enforce cross-product prerequisite patches, you should apply them before applying patch #14050318 No prerequisite on other products details found. Product Families Impacted -------------------------------------------------------------------------------- PRODUCT FAMILY | PRODUCT | LBA -------------------------------------------------------------------------------- oracle.fusionapps.com | acr | NA -------------------------------------------------------------------------------- Patch contains following artifacts that impact the following run-time servers -------------------------------------------------------------------------------- ARTIFACT TYPE | DOMAIN(SERVERS) | EXPECTATION/IMPACT -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- Files included in the patch -------------------------------------------------------------------------------- FILE NAME | FILE TYPE | FILE VERSION -------------------------------------------------------------------------------- build-qtp.xml | ANTSCRIPT | st_fusionapps_11.1.4com/20120 | | 509101010 customtasks.jar | ANTSCRIPT | st_fusionapps_11.1.4com/20120 | | 509101010 earManifest.xml | ANTSCRIPT | st_fusionapps_11.1.4com/20120 | | 509101010 jdom.jar | ANTSCRIPT | st_fusionapps_11.1.4com/20120 | | 509101010 saxon9.jar | ANTSCRIPT | st_fusionapps_11.1.4com/20120 | | 509101010 xmlparserv2.jar | ANTSCRIPT | st_fusionapps_11.1.4com/20120 | | 509101010 -------------------------------------------------------------------------------- The report was generated on: 04-Jan-2013 11:22:02. All timestamps are in Eastern European Time. All log files location :/fa_home/apps_home/fusionapps/applications/admin/FUSION/log Oracle Fusion Applications Patch Manager log :/fa_home/apps_home/fusionapps/applications/admin/FUSION/log/ FAPatchManager_report-patchimpact_20130104112133.log Log Summary :/fa_home/apps_home/fusionapps/applications/admin/FUSION/log/ logsummary_report-patchimpact_20130104112133.html Oracle Fusion Applications Patch Manager completed successfully. In the next run, the log files for this run will be moved from [/fa_home/apps_home/fusionapps/applications/admin/FUSION/log] to [/fa_home/apps_home/fusionapps/applications/admin/FUSION/logarchive/REPORT-PATCHIMPACT/20130104112133].
As you can see, the fapmgr has automatically listed all the bug fixed included in the patch, notified us about the prerequisites (no missing prerequisites in our case) and listed all the files included in the patch. Now right before applying the patch, let’s run a validate report patch to make sure we would not face any issues during the patching:
[oracle@fusionapps bin]$ ./fapmgr.sh validate -patchtop /fa_home/patches Oracle Fusion Applications Patch Manager Version 11.1.4.0.0 Copyright (c) 2012 Oracle Corporation. All rights reserved. Archiving existing log files from [/fa_home/apps_home/fusionapps/applications/admin/FUSION/log] to [/fa_home/apps_home/fusionapps/applications/admin/FUSION/logarchive/REPORT-PATCHIMPACT/20130104112133]. Started validating the Database connection. Completed validating the Database connection. Started checking pre-requisite bug fixes for the patch. Completed checking pre-requisite bug fixes for the patch. Reference number for the current Oracle Fusion Applications Patch Manager run is 41. Started checking if the middleware portion of the patch will make any impact to the system. Please monitor OPatch log file: /fa_home/apps_home/fusionapps/applications/cfgtoollogs/opatch/14050318_Jan_04_2013_11_33_11/ ApplyPrereq2013-01-04_11-33-11AM_1.log Completed checking if the middleware portion of the patch will have an impact on the system. Started running apply pre-reqs. Please monitor OPatch log file: /fa_home/apps_home/fusionapps/applications/cfgtoollogs/opatch/14050318_Jan_04_2013_11_33_11/ ApplyPrereq2013-01-04_11-33-14AM_1.log All apply pre-reqs for middleware artifacts have passed. Started checking for the files that will not be copied. Completed checking for the files that will not be copied. Completed running apply pre-reqs. ================================================================================ Validation of patch is SUCCESSFUL. You can apply the patch. ================================================================================ Generating Diagnostic Report... Diagnostics report is generated at : /fa_home/apps_home/fusionapps/applications/admin/FUSION/log/ FAPMgrDiagnosticsSummary_validate_20130104113257.html. All log files location :/fa_home/apps_home/fusionapps/applications/admin/FUSION/log Oracle Fusion Applications Patch Manager log :/fa_home/apps_home/fusionapps/applications/admin/FUSION/log/ FAPatchManager_validate_20130104113257.log Log Summary :/fa_home/apps_home/fusionapps/applications/admin/FUSION/log/ logsummary_validate_20130104113257.html Oracle Fusion Applications Patch Manager completed successfully. In the next run, the log files for this run will be moved from [/fa_home/apps_home/fusionapps/applications/admin/FUSION/log] to [/fa_home/apps_home/fusionapps/applications/admin/FUSION/logarchive/ 14050318/VALIDATE/41/20130104113257].
The validate phase has checked whether there would be any impact on the running system. In fact, I would notify us if the patch could be applied only in OFFLINE mode or some servers would require a restart after patching. When that part is done, we are now good to go with apply phase:
[oracle@fusionapps bin]$ ./fapmgr.sh apply -patchtop /fa_home/patches -online -stoponerror -workers 4 Oracle Fusion Applications Patch Manager Version 11.1.4.0.0 Copyright (c) 2012 Oracle Corporation. All rights reserved. Archiving existing log files from [/fa_home/apps_home/fusionapps/applications/admin/FUSION/log] to [/fa_home/apps_home/fusionapps/applications/admin/FUSION/logarchive/14050318/VALIDATE/41/ 20130104113257]. Started validating the Database connection. Completed validating the Database connection. Started validating taxonomy URL. Completed validating taxonomy URL. Started checking pre-requisite bug fixes for the patch. Completed checking pre-requisite bug fixes for the patch. Reference number for the current Oracle Fusion Applications Patch Manager run is 42. Started checking if the middleware portion of the patch will make any impact to the system. Please monitor OPatch log file: /fa_home/apps_home/fusionapps/applications/cfgtoollogs/opatch/ 14050318_Jan_04_2013_11_36_34/ ApplyPrereq2013-01-04_11-36-34AM_1.log Completed checking if the middleware portion of the patch will have an impact on the system. Started running apply pre-reqs. Please monitor OPatch log file: /fa_home/apps_home/fusionapps/applications/cfgtoollogs/opatch/ 14050318_Jan_04_2013_11_36_34/ ApplyPrereq2013-01-04_11-36-37AM_1.log All apply pre-reqs for middleware artifacts have passed. Started checking for the files that will not be copied. Completed checking for the files that will not be copied. Started identifying Post Apply tasks. Completed identifying Post Apply tasks. Started applying the Middleware Components of the patch. Please monitor OPatch log file: /fa_home/apps_home/fusionapps/applications/cfgtoollogs/opatch/14050318_Jan_04_2013_11_36_34/ apply2013-01-04_11-36-42AM_1.log Completed applying the Middleware Components of the patch. -------------------------------------------------------------------------------- Generating the data fixes XML file. Generated patch inventory file: /fa_home/apps_home/fusionapps/applications/faPatchInventory/fusionAppsPatchHistory.xml Generating Diagnostic Report... Diagnostics report is generated at : /fa_home/apps_home/fusionapps/applications/admin/FUSION/log/ FAPMgrDiagnosticsSummary_apply_20130104113618.html. All log files location :/fa_home/apps_home/fusionapps/applications/admin/FUSION/log Oracle Fusion Applications Patch Manager log :/fa_home/apps_home/fusionapps/applications/admin/FUSION/log/ FAPatchManager_apply_20130104113618.log Log Summary :/fa_home/apps_home/fusionapps/applications/admin/FUSION/log/ logsummary_apply_20130104113618.html Oracle Fusion Applications Patch Manager completed successfully. In the next run, the log files for this run will be moved from [/fa_home/apps_home/fusionapps/applications/admin/FUSION/log] to [/fa_home/apps_home/fusionapps/applications/admin/FUSION/logarchive/14050318/APPLY/42/ 20130104113618].
The patch has now been applied in online mode using 4 workers (the same functionality as used in eBS). Stoponerror option is recommended when applying the patch online, so that you could manually fix the issue and then restart the patching manager again. There are also another good features available, I would blog about them, once I get a chance to get my hands dirty there, but for overview look and feel – I hope I’ve provided some insight on Fusion Applications patching.
Oracle APPS DBA days 