Tuesday, August 28, 2012

Applying patchs in fusion application through fapmgr

Applying Patchs in the Fusion Applications Through the fapmgr [Fusion applications patch manager]

The fusion applications we can apply the patch through the new utility knows as fapmgr [fapatchmanager] ..In  fapmgr you can validate the patch and get the  report  .. the fapmgr identifies the oracle home in which it should apply the patch ..

Step1  Download the recommended patch's from the MOS and unzip in the patch_top of your Application Box
once you unzip the patch then the fapmgr.sh is located under the AD_TOP in the fusion applications..go to $AD_TOP

[oracle@fahbin]$ pwd /u01/oracle/fa/products/fusionapps/applications/lcm/ad/bin

-rwxr-x--- 1 oracle oinstall  8721 Jul 17 23:55 adadmin.sh
-rwxr-x--- 1 oracle oinstall  8310 Jul 17 23:55 adctrl.sh
-rwxr-x--- 1 oracle oinstall 15879 Jul 17 23:55 adsetenv.sh
-rwxr-x--- 1 oracle oinstall  5946 Jul 17 23:55 datafix.sh
-rwxr-x--- 1 oracle oinstall  5791 Jul 17 23:55 fapmgr.sh
-rwxr-x--- 1 oracle oinstall  7190 Jul 17 23:55 fastartstop.sh
-rwxr-x--- 1 oracle oinstall  4516 Jul 17 23:55 homechecker.sh
-rwxr-x--- 1 oracle oinstall  4532 Jul 17 23:55 provchecker.sh

Step 2 

Validate the patch before applying in Fusion applications 

Syntax:$APPL_TOP/lcm/ad/bin/fapmgr.sh validate -patchtop <location-of the patch>


[oracle@fahtestdb 14268020]$  /u01/oracle/fa/products/fusionapps/applications/lcm/ad/bin/fapmgr.sh validate -patchtop /u01/oracle/fa/Patch/14268020
Oracle Fusion Applications Patch Manager Version 11.1.4.0.0
Copyright (c) 2012 Oracle Corporation. All rights reserved.
Started validating the Database connection.
WLS ManagedService is not up running. Fall back to use system properties for configuration.
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 124.
Started checking if the middleware portion of the patch will make any impact to the system.
Please monitor OPatch log file: /u01/oracle/fa/products/fusionapps/applications/cfgtoollogs/opatch/14268020_Aug_28_2012_11_12_11/ApplyPrereq2012-08-28_11-12-25AM_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: /u01/oracle/fa/products/fusionapps/applications/cfgtoollogs/opatch/14268020_Aug_28_2012_11_12_11/ApplyPrereq2012-08-28_11-12-29AM_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 : /u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/FAPMgrDiagnosticsSummary_validate_20120828111149.html.

All log files location        :/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log
Oracle Fusion Applications Patch Manager log :/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/FAPatchManager_validate_20120828111149.log
Log Summary                   :/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/logsummary_validate_20120828111149.html 
Oracle Fusion Applications Patch Manager completed successfully.
Check the html output for the patch and there are two files to Be diagnostics's 
The location of the logfile  for the fapmgr is $APPL_TOP/admin/FUSION/log

we can locate two log files in this location
[1]FAPMgrDiagnosticsSummary_validate_<yyyymmdd>.html and [2]logsummary_validate_<yyyymmdd>.html

Step 2

We can apply the patch on two different type of mode's 
[1] ONLINE
[2] OFFLINE

Applying the patch in online mode in fusion applications

When you apply the patch in the online mode the respective  managed server's which is mentioned in The patch will be restarted ...
But if the patch is  applied  on  the offline mode the managed server's will not be restarted  but we have to do some steps mannulay to apply the patch

For some of the patch's it is recommended to apply it in the online mode
when you are Proceeding with the online mode then you have to specify two parameter's for it  -stoponerror or continueonerror

Syntax: $APPL_TOP/lcm/ad/bin fapmgr.sh apply -patchtop <location_of_patch_file> -online <-stoponerror [or] continueonerror> 

[oracle@fahtestdb 14268020]$  /u01/oracle/fa/products/fusionapps/applications/lcm/ad/bin/fapmgr.sh apply  -patchtop /u01/oracle/fa/Patch/14268020 -online -stoponerror
Oracle Fusion Applications Patch Manager Version 11.1.4.0.0
Copyright (c) 2012 Oracle Corporation. All rights reserved.

Started validating the Database connection.
WLS ManagedService is not up running. Fall back to use system properties for configuration.
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 126.

Started checking if the middleware portion of the patch will make any impact to the system.
Please monitor OPatch log file: /u01/oracle/fa/products/fusionapps/applications/cfgtoollogs/opatch/14268020_Aug_28_2012_11_46_18/ApplyPrereq2012-08-28_11-46-33AM_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: /u01/oracle/fa/products/fusionapps/applications/cfgtoollogs/opatch/14268020_Aug_28_2012_11_46_18/ApplyPrereq2012-08-28_11-46-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 SHUTDOWN of managed server(s). This might take a while.
Oracle Fusion Applications Patch Manager will attempt to stop the following managed server(s):
Server=[PayableServer_1],Domain=[FinancialDomain]
Server=[HelpPortalServer_1],Domain=[CommonDomain]
Server=[GeneralLedgerServer_1],Domain=[FinancialDomain]
Please monitor OPatch log file: /u01/oracle/fa/products/fusionapps/applications/cfgtoollogs/opatch/lifecycle_2012-08-28_11-46-33AM/Stop_Servers_Parallel_Master2012-08-28_11-47-14AM_1.log
Life cycle operation [stopManagedServers] on managed server [PayableServer_1] of domain [FinancialDomain] successful.
Life cycle operation [stopManagedServers] on managed server [HelpPortalServer_1] of domain [CommonDomain] successful.
Life cycle operation [stopManagedServers] on managed server [GeneralLedgerServer_1] of domain [FinancialDomain] successful.
Completed SHUTDOWN of managed server(s).

Started applying the Middleware Components of the patch.
Please monitor OPatch log file: /u01/oracle/fa/products/fusionapps/applications/cfgtoollogs/opatch/14268020_Aug_28_2012_11_46_18/apply2012-08-28_11-48-04AM_1.log
Completed applying the Middleware Components of the patch.

Started STARTUP of managed server(s). This might take a while.
Oracle Fusion Applications Patch Manager will attempt to start the following managed server(s):
Server=[PayableServer_1],Domain=[FinancialDomain]
Server=[HelpPortalServer_1],Domain=[CommonDomain]
Server=[GeneralLedgerServer_1],Domain=[FinancialDomain]
Please monitor OPatch log file: /u01/oracle/fa/products/fusionapps/applications/cfgtoollogs/opatch/lifecycle_2012-08-28_11-46-33AM/Start_Servers_Parallel_Master2012-08-28_11-48-24AM_1.log
Life cycle operation [startManagedServers] on managed server [PayableServer_1] of domain [FinancialDomain] successful.
Life cycle operation [startManagedServers] on managed server [HelpPortalServer_1] of domain [CommonDomain] successful.
Life cycle operation [startManagedServers] on managed server [GeneralLedgerServer_1] of domain [FinancialDomain] successful.
Completed STARTUP of managed server(s).

--------------------------------------------------------------------------------
Generating the data fixes XML file.

Generated patch inventory file: /u01/oracle/fa/products/fusionapps/applications/faPatchInventory/fusionAppsPatchHistory.xml

Generating Diagnostic Report...
Diagnostics report is generated at : /u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/FAPMgrDiagnosticsSummary_apply_20120828114555.html.

All log files location                       :/u01/oracle/fa/products/fusionapps/applications/adm/FUSION/log
Oracle Fusion Applications Patch Manager log :/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/FAPatchManager_apply_20120828114555.log
Log Summary                                  :/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/logsummary_apply_20120828114555.html
Oracle Fusion Applications Patch Manager completed successfully.


In the next run, the log files for this run will be moved from [/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log] to [/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/logarchive/14268020/APPLY/126/20120828114555].

Monitoring the logfile for the patch when it does the parallel operation of restartig the managed Server's

The above patch requires to restart the three managed server's to Complete sucessfully.. monitory the logfile for the patch's process on restarting the managed server's

Server's[Aug 28, 2012 11:48:24 AM]   All prerequisite checks passed for start operation.
[Aug 28, 2012 11:48:26 AM]   ---------Parallel start operation----------
[Aug 28, 2012 11:48:26 AM]
[Aug 28, 2012 11:48:26 AM]   [FMW] Number of requests for parallel start operation: 3
[Aug 28, 2012 11:48:26 AM]   [FMW]
[Aug 28, 2012 11:48:26 AM]   [FMW] Number of threads to be created: 2
[Aug 28, 2012 11:48:26 AM]   [FMW] Thread name="Thread-0", Servename="HelpPortalServer_1", Domain name="CommonDomain", Please monitor the log file: "/u01/oracle/fa/products/fusionapps/applications/cfgtoollogs/opatch/lifecycle_2012-08-28_11-46-33A/Start_Server_HelpPortalServer_1_CommonDomain2012-08-28_11-48-26AM_5.log"
[Aug 28, 2012 11:48:26 AM]   [FMW] Thread name="Thread-1", Server name="PayableServer_1", Domain name="FinancialDomain", Please monitor the log file: "/u01/oracle/fa/products/fusionapps/applications/cfgtoollogs/opatch/lifecycle_2012-08-28_11-46-33AM/Start_Server_PayableServer_1_FinancialDomain2012-08-28_11-48-26AM_6.log"
[Aug 28, 2012 11:48:26 AM]   [FMW] Thread name="Thread-1", Server name="GeneralLedgerServer_1", Domain name="FinancialDomain", Please monitor the log file: "/u01/oracle/fa/products/fusionapps/applications/cfgtoollogs/opatch/lifecycle_2012-08-28_11-46-33A /Start_Server_GeneralLedgerServer_1_FinancialDomain2012-08-28_11-48-26AM_6.log"
[Aug 28, 2012 11:48:26 AM]   [FMW]
[Aug 28, 2012 11:53:47 AM]   ----------Status of parallel start operation----------
[Aug 28, 2012 11:53:47 AM]
[Aug 28, 2012 11:53:47 AM]   Parallel start operation completed successfully for the following servers only [PayableServer_1, HelpPortalServer_1, GeneralLedgerServer_1]

NOTE:Also verify the  log file and the html out put of the patch to conform it is successfully Applied


 

No comments:

Post a Comment