Oracle Fusion Applications: August 2012

Thursday, August 30, 2012

fapmgr: Running Patching Reports in the fusion application

Running Patching Reports using fapmgr in Fusion applications

In fapmgr we can use the report command with different parameter's[-patchimpact, -listpatches ,-listcomps,-isapplied,-patchprogress] to generate various information about the Patches

[1]Running the Patch Impact Report

By using the Patch impact report report we can generate the report of the patch's effect and the actions so of the patches may bring down so of the managed server's in the process of applying ...

Syntax: $APPL_TOP/lcm/ad/bin/fapmgr.sh report -patchimpact -patchtop <location_of_the_patch> -reportwidth WIDE

[oracle@fahapp 14268020]$ /u01/oracle/fa/products/fusionapps/applications/lcm/ad/bin/fapmgr.sh report -patchimpact -patchtop /u01/oracle/fa/Patch/14268020 -reportwidth WIDE

Oracle Fusion Applications Patch Manager Version 11.1.4.0.0

Archiving existing log files from [/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log] to [/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/logarchive/REPORT-LISTPATCHES/20120829152800].

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 running apply pre-reqs.

Please monitor OPatch log file: /u01/oracle/fa/products/fusionapps/applications/cfgtoollogs/opatch/14268020_Aug_29_2012_15_29_23/ApplyPrereq2012-08-29_15-29-23PM_1.log

All apply pre-reqs for middleware artifacts have passed.

Patch Impact Report

Patch Number: 14268020

Fusion Applications Oracle Home: /u01/oracle/fa/products/fusionapps/applications

Language: US

Platform: Generic

Bug Fixes

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

BUG NO. | BUG DESCRIPTION | Exists in OracleHome

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

14268020 | PROBLEM IN MODIFYING DATA ACCESS SET | No

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Prerequisite Bug Fixes Not in FA_ORACLE_HOME: No prerequisite bug fixes missing for patch #14268020

Prerequisites on other products: Although Patch Manager does not enforce cross-product prerequisite patches, you should apply them before applying patch #14268020

No prerequisite on other products details found.

Product Families Impacted

------------------------------------------------------------------------------------------------------------------------------------

PRODUCT FAMILY | PRODUCT | LBA

------------------------------------------------------------------------------------------------------------------------------------

oracle.fusionapps.fin | gl | FinGlSharedSetupDAS

------------------------------------------------------------------------------------------------------------------------------------

Patch contains following artifacts that impact the following run-time servers

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

ARTIFACT TYPE | DOMAIN(SERVERS) | EXPECTATION/IMPACT

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Flexfields(FndSetup.ear) | CommonDomain(HelpPortalServer_1 ) | Impacted managed servers will be bounced.

JEE(EarFinLedger.ear) | FinancialDomain(GeneralLedgerServer_1) | Impacted managed servers will be bounced.

JEE(EarFinPayables.ear) | FinancialDomain(PayableServer_1) | Impacted managed servers will be bounced.

------------------------------------------------------------------------------------------------------------------------------------

Files included in the patch

------------------------------------------------------------------------------------------------------------------------------------

FILE NAME | FILE TYPE | FILE VERSION

------------------------------------------------------------------------------------------------------------------------------------

AdfFinGlSharedSetupDASModel.jar | JEE | st_fusionapps_11.1.4fin/20120814015518

SvcFinGlSharedSetupDASModel_Common.jar | JEE | st_fusionapps_11.1.4fin/20120814015518

SvcFinGlSharedSetupDASModel_MiddleTier.jar | JEE | st_fusionapps_11.1.4fin/20120814015518

------------------------------------------------------------------------------------------------------------------------------------

Prerequisite Bug Fixes Not in FA_ORACLE_HOME: No prerequisite bug fixes missing for patch #14268020

Prerequisites on other products: Although Patch Manager does not enforce cross-product prerequisite patches, you should apply them before applying patch #14268020

No prerequisite on other products details found.

The report was generated on: 29-Aug-2012 15:29:26. All timestamps are in Gulf Standard Time.

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_report-patchimpact_20120829152907.log

Log Summary :/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/logsummary_report-patchimpact_20120829152907.html

Oracle Fusion Applications Patch Manager completed successfully.

Note: In This particular patch it restart's three managed server while applying so by running the patch impact report we are able to view the impact and according to that we can plan the Strateregy

[2]Running the Applied Patches Report In Fusion Applications [listpatches]

To list all the patch's which is applied to one particular domain or the whole system we need to use the -listpatchs command with the report command

listpatches can be executed in two modes [1] for single domain or [2] for the full instance

if we need to use the Single domain then we have to use the comps parameter to specify the specify component which need's to be checked

Running the listpatces with the specific domain

to Know the list op patches applied to the particular artifact of the fusion applications then we need to specify the parameter -comps and we need to specify name of the component which we need details

Syntax:$APPL_TOP/lcm/ad/bin/fapmgr.sh report -listpatches -comps<component_name> -reportwith<WIDE/NORMAL>

[oracle@fahapp 14268020]$ /u01/oracle/fa/products/fusionapps/applications/lcm/ad/bin/fapmgr.sh report -listpatches -comps oracle.fusionapps.fin -reportwidth WIDE

Oracle Fusion Applications Patch Manager Version 11.1.4.0.0

Started validating the Database connection.

WLS ManagedService is not up running. Fall back to use system properties for configuration.

Completed validating the Database connection.

Report Name: Patches Applied

Report for: FUSION [/u01/oracle/fa/products/fusionapps/applications]

ProductFamily (OUI Component) :: Oracle Fusion Financials (oracle.fusionapps.fin)

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

PATCH NO. | LANGUAGE | PATCH TYPE | DATE APPLIED (mm-dd-yyyyhh:mm:ss) | BUGS FIXED

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------

14268020 | American English | Standard | 08-29-2012 15:40:06 | 14268020

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The report was generated on: 29-Aug-2012 15:52:58. All timestamps are in Gulf Standard Time.

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_report-listpatches_20120829155243.log

Log Summary :/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/logsummary_report-listpatches_20120829155243.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/REPORT-LISTPATCHES/20120829155243].

Running the listpatches for the full system [all Domain's]

Syntax: $APPL_TOP/lcm/ad/bin/fapmgr.sh report -listpatches reportwith <NORMAL/WIDE>

If we need to know the details of Patches applied on the all the artifact's [whole system] then we need to run the report command without the -comps

Syntax : $APPL_TOP/lcm/ad/bin fapmgr.sh report -listpatches -reportwidth WIDE

[oracle@fahapp 14268020]$ /u01/oracle/fa/products/fusionapps/applications/lcm/ad/bin/fapmgr.sh report -listpatches -reportwidth WIDE

Oracle Fusion Applications Patch Manager Version 11.1.4.0.0

Started validating the Database connection.

WLS ManagedService is not up running. Fall back to use system properties for configuration.

Completed validating the Database connection.

Report Name: Patches Applied

Report for: FUSION [/u01/oracle/fa/products/fusionapps/applications]

ProductFamily (OUI Component) :: Oracle Fusion Common Artifacts (oracle.fusionapps.com)

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

PATCH NO. | LANGUAGE | PATCH TYPE | DATE APPLIED (mm-dd-yyyy hh:mm:ss) | BUGS FIXED

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

22222222 | American English | MAINTENANCE-PACK | 08-23-2012 03:29:40 | 22222222

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

ProductFamily (OUI Component) :: Oracle Fusion Financials (oracle.fusionapps.fin)

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

PATCH NO. | LANGUAGE | PATCH TYPE | DATE APPLIED (mm-dd-yyyyhh:mm:ss) | BUGS FIXED

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

14268020 | American English | Standard | 08-29-2012 15:40:06 | 14268020

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The report was generated on: 29-Aug-2012 15:53:42. All timestamps are in Gulf Standard Time.

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_report-listpatches_20120829155326.log

Log Summary :/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/logsummary_report-listpatches_20120829155326.html

Oracle Fusion Applications Patch Manager completed successfully.

By executing this command will help us to find all the patch applied on the system ..................

Running the listpatches [list of patches installed in the fusion environment for multiple domain]

In the list patches command we can collect the details of patch for specify a separate domain or Artifacts

and for whole system

Running fapmgr with report listcomps -comps

To know the list of patches and the product family for the particular component we need to use the -comps and we can specify the list of components with the coma specified to get the details for more that one domain

Syntax: $APPL_TOP/lcm/ad/bin/fapmgr.sh report -listpatches -comps <componentname1,....,componentanem<n> > -outputfile <filename> - reportwidth <NORMAL/WIDE>

comps :we have to specify the oracle component name that had been installed in the system to find only the specific details about that product ,we can get multiple product details by adding the components name separating with coma

outputfile :the output of the command will be stored in the file specified here

reportwidth the width of the report will be specified as NORMAL OR WIDE if we use wide than the tabular columns appear will be displayed correctly

[oracle@fahapp 14370658]$ /u01/oracle/fa/products/fusionapps/applications/lcm/ad/bin/fapmgr.sh report -listpatches -comps oracle.fusionapps.fin,oracle.fusionapps.com -outputfile comp_reports.rxt -reportwidth WIDE

Oracle Fusion Applications Patch Manager Version 11.1.4.0.0

Started validating the Database connection.

WLS ManagedService is not up running. Fall back to use system properties for configuration.

Completed validating the Database connection.

Report Name: Patches Applied

Report for: FUSION [/u01/oracle/fa/products/fusionapps/applications]

ProductFamily (OUI Component) :: Oracle Fusion Common Artifacts (oracle.fusionapps.com)

------------------------------------------------------------------------------------------------------------------------------------

PATCH NO. | LANGUAGE | PATCH TYPE | DATE APPLIED (mm-dd-yyyy | BUGS FIXED

| | | hh:mm:ss) |

------------------------------------------------------------------------------------------------------------------------------------

22222222 | American English | MAINTENANCE-PACK | 08-23-2012 03:29:40 | 22222222

------------------------------------------------------------------------------------------------------------------------------------

ProductFamily (OUI Component) :: Oracle Fusion Financials (oracle.fusionapps.fin)

------------------------------------------------------------------------------------------------------------------------------------

PATCH NO. | LANGUAGE | PATCH TYPE | DATE APPLIED (mm-dd-yyyy | BUGS FIXED

| | | hh:mm:ss) |

------------------------------------------------------------------------------------------------------------------------------------

14268020 | American English | Standard | 08-29-2012 15:40:06 | 14268020

14370658 | American English | Standard | 08-30-2012 19:23:59 | 14370658

------------------------------------------------------------------------------------------------------------------------------------

The report was generated on: 30-Aug-2012 21:52:42. All timestamps are in Gulf Standard Time.

The report file is created at: /u01/oracle/fa/Patch/14370658/comp_reports.rxt

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_report-listpatches_20120830215226.log

Log Summary :/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/logsummary_report-listpatches_20120830215226.html

Oracle Fusion Applications Patch Manager completed successfully.

Running listcomps [list of components installed in the fusion applications]

To know the list of components installed in the fusion applications we need to run the listcomps

syntax :$APPL_TOP/lcm/ad/bin/fapmgr.sh report -listcomps -reportwidth WIDE

[oracle@fahapp ~]$ /u01/oracle/fa/products/fusionapps/applications/lcm/ad/bin/fapmgr.sh report -listcomps -reportwidth WIDE
Oracle Fusion Applications Patch Manager Version 11.1.4.0.0
Copyright (c) 2012 Oracle Corporation. All rights reserved.

Archiving existing log files from [/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log] to [/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/logarchive/REPORT-LISTPATCHES/20120902153419].

Started validating the Database connection.
WLS ManagedService is not up running. Fall back to use system properties for configuration.
Completed validating the Database connection.

Report Name: Product Families
Report for: FUSION [/u01/oracle/fa/products/fusionapps/applications]
------------------------------------------------------------------------------------------------------------------------------------
OUI COMPONENT | VERSION | PRODUCT FAMILY | DESCRIPTION
------------------------------------------------------------------------------------------------------------------------------------
oracle.fusionapps.top | 11.1.4.0.0 | Oracle Fusion Applications 11.1.| Oracle Fusion Applications
| | 4.0.0 |
oracle.swd.oui | 11.1.0.9.0 | Oracle Universal Installer 11.1.| Installs the components developed using the
| | 0.9.0 | Oracle Software Packager.
oracle.swd.opatch | 11.1.0.9.5 | Oracle One-Off Patch Installer 1| Oracle One-Off Patch Installer
| | 1.1.0.9.5 |
oracle.fusionapps.lcm | 11.1.4.0.0 | Oracle Fusion Patch Manager arti| Oracle Fusion Patch Manager artifacts
| | facts 11.1.4.0.0 |
oracle.fusionapps.grc | 11.1.4.0.0 | Oracle Fusion Governance, Risk, | Oracle Fusion Governance, Risk, and Complia
| | and Compliance 11.1.4.0.0 | nce
oracle.fusionapps.fscm | 11.1.4.0.0 | Oracle Fusion Financials Supply | Oracle Fusion Financials Supply Chain Manag
| | Chain Management 11.1.4.0.0 | ement
oracle.fusionapps.scm | 11.1.4.0.0 | Oracle Fusion Supply Chain Manag| Oracle Fusion Supply Chain Management
| | ement 11.1.4.0.0 |
oracle.fusionapps.hcm | 11.1.4.0.0 | Oracle Fusion Human Capital Mana| Oracle Fusion Human Capital Management
| | gement 11.1.4.0.0 |
oracle.fusionapps.fin | 11.1.4.0.0 | Oracle Fusion Financials 11.1.4.| Oracle Fusion Financials
| | 0.0 |
oracle.fusionapps.crm | 11.1.4.0.0 | Oracle Fusion Customer Relations| Oracle Fusion Customer Relationship Managem
| | hip Management 11.1.4.0.0 | ent
oracle.fusionapps.atf | 11.1.4.0.0 | Oracle Fusion Applications Techn| Oracle Fusion Applications Technology
| | ology 11.1.4.0.0 |
oracle.fusionapps.com | 11.1.4.0.0 | Oracle Fusion Common Artifacts 1| Oracle Fusion Common Artifacts
| | 1.1.4.0.0 |
oracle.fusionapps.ic | 11.1.4.0.0 | Oracle Fusion Incentive Compensa| Oracle Fusion Incentive Compensation
| | tion 11.1.4.0.0 |
oracle.fusionapps.prj | 11.1.4.0.0 | Oracle Fusion Projects 11.1.4.0.| Oracle Fusion Projects
| | 0 |
oracle.fusionapps.ahc | 11.1.4.0.0 | Oracle Fusion Help 11.1.4.0.0 | Oracle Fusion Help
oracle.fusionapps.prc | 11.1.4.0.0 | Oracle Fusion Procurement 11.1.4| Oracle Fusion Procurement
| | .0.0 |
------------------------------------------------------------------------------------------------------------------------------------

The report was generated on: 02-Sep-2012 15:35:37. All timestamps are in Gulf Standard Time.
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_report-listcomps_20120902153523.log
Log Summary :/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/logsummary_report-listcomps_20120902153523.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/REPORT-LISTCOMPS/20120902153523].

Running listcomps for the specific component's [domain]

To Know the list of component's installed in the specific domain [artifact's ] we have to specify components name we can speccify the multiply components with coma separated to know the details for each component

Syntax : $APPL_TOP/lcm/ad/bin/faomgr.sh report -listcomps -comps <component names> -outputfile <outputfile name >-reportwidth WIDE

[oracle@fahapp ~]$ /u01/oracle/fa/products/fusionapps/applications/lcm/ad/bin/fapmgr.sh report -listcomps -comps oracle.fusionapps.fin,oracle.fusionapps.com -reportwidth WIDE
Oracle Fusion Applications Patch Manager Version 11.1.4.0.0
Copyright (c) 2012 Oracle Corporation. All rights reserved.

Archiving existing log files from [/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log] to [/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/logarchive/REPORT-LISTCOMPS/20120902153523].

Started validating the Database connection.
WLS ManagedService is not up running. Fall back to use system properties for configuration.
Completed validating the Database connection.

Report Name: Product Families
Report for: FUSION [/u01/oracle/fa/products/fusionapps/applications]
------------------------------------------------------------------------------------------------------------------------------------
OUI COMPONENT | VERSION | PRODUCT FAMILY | DESCRIPTION
------------------------------------------------------------------------------------------------------------------------------------
oracle.fusionapps.fin | 11.1.4.0.0 | Oracle Fusion Financials 11.1.4.0.0 | Oracle Fusion Financials

oracle.fusionapps.com | 11.1.4.0.0 | Oracle Fusion Common Artifacts 11.1.4.0.0 | Oracle Fusion Common Artifacts

------------------------------------------------------------------------------------------------------------------------------------

The report was generated on: 02-Sep-2012 15:42:14. All timestamps are in Gulf Standard Time.
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_report-listcomps_20120902154200.log
Log Summary :/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/logsummary_report-listcomps_20120902154200.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/REPORT-LISTCOMPS/20120902154200].

Patch applied status report -isapplied for one particular bug or patch number

TO check whether the particular patch or bug related patch had been applied in the fusion artifact's we need to run isapplied

Syntax :$APPL_TOP/lcm/ad/bin/fapmgr.sh report -isapplied -bug <bugnumber> -reportwidth WIDE

[oracle@fahapp ~]$ /u01/oracle/fa/products/fusionapps/applications/lcm/ad/bin/fapmgr.sh report -isapplied -bug 14268020 -reportwidth WIDE
Oracle Fusion Applications Patch Manager Version 11.1.4.0.0
Copyright (c) 2012 Oracle Corporation. All rights reserved.

Archiving existing log files from [/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log] to [/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/logarchive/REPORT-LISTCOMPS/20120902154200].

Started validating the Database connection.
WLS ManagedService is not up running. Fall back to use system properties for configuration.
Completed validating the Database connection.

Report Name: Patch Status
Report for: FUSION [/u01/oracle/fa/products/fusionapps/applications]
------------------------------------------------------------------------------------------------------------------------------------
BUG NO. | OUI COMPONENT | STATUS | PATCH NO. | DATE APPLIED (mm-dd-yyyy
| | | | hh:mm:ss)
------------------------------------------------------------------------------------------------------------------------------------
14268020:US | oracle.fusionapps.fin | Applied | 14268020 | 08-29-2012 15:40:06
------------------------------------------------------------------------------------------------------------------------------------

The report was generated on: 02-Sep-2012 15:52:35. All timestamps are in Gulf Standard Time.
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_report-isapplied_20120902155220.log
Log Summary :/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/logsummary_report-isapplied_20120902155220.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/REPORT-ISAPPLIED/20120902155220].

Running Patch Progress Report

Patch progress report is used to when your are executing the patch and by using the patch progress report

Syntax :$APPL_TOP/lcm/ad/bin/fapmgr.sh -patchprogress

[oracle@fahapp ~]$ /u01/oracle/fa/products/fusionapps/applications/lcm/ad/bin/fapmgr.sh report -patchprogress

Oracle Fusion Applications Patch Manager Version 11.1.4.0.0

Started validating the Database connection.

WLS ManagedService is not up running. Fall back to use system properties for configuration.

Completed validating the Database connection.

There are no ACTIVE Fusion Application patching sessions.

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_report-patchprogress_20120908114751.log

Log Summary :/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/logsummary_report-patchprogress_20120908114751.html

Oracle Fusion Applications Patch Manager completed successfully.

[oracle@fahapp ~]$ /u01/oracle/fa/products/fusionapps/applications/lcm/ad/bin/fapmgr.sh report -patchprogress

Oracle Fusion Applications Patch Manager Version 11.1.4.0.0

Started validating the Database connection.

WLS ManagedService is not up running. Fall back to use system properties for configuration.

Completed validating the Database connection.

Current Fusion Application patching session details are :

Session id : 122

Session mode : APPLY

Status : ACTIVE

Patch number : 14050318

Commandline args : apply -patchtop /u01/oracle/fa/Patch -online -stoponerror -workers 10

Generating Diagnostic Report...

Diagnostics report is generated at : /u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/FAPMgrDiagnosticsSummary.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_report-patchprogress_20120908115052.log

Log Summary :/u01/oracle/fa/products/fusionapps/applications/admin/FUSION/log/logsummary_report-patchprogress_20120908115052.html

Oracle Fusion Applications Patch Manager completed successfully.

Current Log file Location :$APPL_TOP/admin/FUSION/log

only the current log files and the last executed patch log files are stored in this location remaining log files are stored in the different location know as logarchive

when you are executing the next fapmgr session automatically it stores all the log files to the log archive location for the previous patch

Archive log file location: $APPL_TOP/admin/FUSION/logarchive

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

Monday, August 27, 2012

Adding the extract in the GoldenGate with thread options for RAC database

Adding the extract in the Golden Gate with thread options

To add the extract in the golden latest version 11.2. we have to download the golden gate from the edelivery .oracle.com fusion middle ware and unzip in the appropriate location if you are using the RAC database unzip the contents in the shared directory which is accessible to all the nodes

Step 1

For golden gate there is a command prompt knows as ggsci and go to the golden gate root directory [the directory which you have unzipped the contents of the file and type ./ggsci

oraprod@db[PROD1]:$ ./ggsci

Oracle GoldenGate Command Interpreter for Oracle

Version 11.2.1.0.1 OGGCORE_11.2.1.0.1_PLATFORMS_120423.0230

HP/UX, IA64, 64bit (optimized), Oracle 10g on Apr 23 2012 22:20:31

GGSCI (db) 1>

Now you will get the ggsci command prompt

Step 2

Creating the sub directories there are may sub directories to be created as the empty directory for various operations of the gg

GGSCI (db) 3> create SUBDIRS

Creating subdirectories under current directory /fah/ggtest/gg

Parameter files /fah/ggtest/gg/dirprm: created

Report files /fah/ggtest/gg/dirrpt: created

Checkpoint files /fah/ggtest/gg/dirchk: created

Process status files /fah/ggtest/gg/dirpcs: created

SQL script files /fah/ggtest/gg/dirsql: created

Database definitions files /fah/ggtest/gg/dirdef: created

Extract data files /fah/ggtest/gg/dirdat: created

Temporary files /fah/ggtest/gg/dirtmp: created

Stdout files /fah/ggtest/gg/dirout: created

Step 3

exit from the ggsci command prompt and create the necessary Parameter files and add it in the dirprm directory

GGSCI (db) 3> exit

oraprod@db[PROD1]:$ cd dirprm

oraprod@db[PROD1]:$ ls

defgen.prm jagent.prm mgr.prm setupini.prm setupr.prm trane.prm tranp.prm tranr.prm

Step 4

start the manager first

GGSCI (db) > start MGR

Manager started.

GGSCI (db) > info all

Program Status Group Lag at Chkpt Time Since Chkpt

MANAGER RUNNING

Step 5

Add the extract into the gg and check the extract according to the number of instance's we need to specify the thread if you have more that 2 nodes then you have to specify according to it

GGSCI (db) > ADD EXTRACT TRANE, TRANLOG, BEGIN NOW, THREADS 2

EXTRACT added.

GGSCI (db) > info *

EXTRACT TRANE Initialized 2012-08-26 12:13 Status STOPPED

Checkpoint Lag 00:00:00 (updated 00:00:04 ago)

Log Read Checkpoint Oracle Redo Logs

2012-08-27 12:11:10 Thread 1, Seqno 0, RBA 0

SCN 0.0 (0)

Log Read Checkpoint Oracle Redo Logs

2012-08-27 12:11:10 Thread 2, Seqno 0, RBA 0

SCN 0.0 (0)

EXTRACT TRANE Last Started 2012-08-26 12:13 Status RUNNING
Checkpoint Lag 00:00:00 (updated 00:00:10 ago)
Log Read Checkpoint Oracle Redo Logs
2012-08-27 13:57:41 Thread 1, Seqno 73117, RBA 97613824
Log Read Checkpoint Oracle Redo Logs
2012-08-27 13:57:41 Thread 2, Seqno 85862, RBA 82908040

OCI Error ORA-00001: unique constraint violated

The replicate will be in a a banded state and when you get this error in the gg replicate then you have to check the data from the source table and the target table...
Some of the data which is present in the source table is already present in the target table

we need to check the records from two table on which the error is produced there is a solution for this ... by adding the rep parameter on the replicate parameter file

Step1

Once the process is getting abandoned we need to check the report file of the particular process

GGSCI (fahdb.) 2> view report TRANR1

and find the details of the error in the report file

2012-08-26 14:55:33 WARNING OGG-00869 OCI Error ORA-00001: unique constraint (constraint _name) violated (status = 1),
2012-08-26 14:55:33 WARNING OGG-01004 Aborted grouped transaction on 'table_name', Database error 1 (OCI Error ORA-00001: unique constraint (constraint _name) violated (status = 1), <sql statment>
2012-08-26 14:55:33 WARNING OGG-01003 Repositioning to rba 846885 in seqno 150

Step 2
Conform from the source and the target side whether the records which is present in the source is present in the target and the source is trying to send the record which is already present in the target table,,, this cause's the ORA-00001 .. the unique constraint of the target table is violated because the data is already present in the table but the source is trying to insert the same record...
Query both the tables involved in and verify the record

Step 3
There are two ways to rectify the error we can do it globally of all the tables are we can do it only for the particular table
here we followed the global strategy ... if your replicate and the extract using more then one table and causing the error .. it is wise to follow the global strategy
By add in the parameter in the parameter file we can avoid this error and we can create the discard file to hold the discarded data[ if the data which is already present in the Target then that data will be moved into the discard file]
Step4

We need to add the parameter in the extract or replicate's parameter file
Go to the root directory of the gg and the navigate to dirprm which hold's all the parameter file's for the process

[oracle@fahdb dirprm]$ pwd
/u01/app/oracle/product/gg/dirprm

[oracle@fahdb dirprm]$ ls
defgen.prm mgr.prm setupi1.prm trane.prm tranr1.prm
setupe.prm setupp1.prm tranp1.prm

Parameter with discard file

ADD THE PARAMETER REPERROR (1, DISCARD)

Advantage of creating the discard file is we can check the duplicate record's which are tried to insert in to the target table all the duplicate records will be stored in the discard file

Parameter with out discard file

ADD THE PARAMETER REPERROR (1)

once the parameter is added we can start the replicate if the replicate start's fine and check the discard file and wait until the all the trail files are processed .. once all the trail files are processed the yo can comment out the parameter if it is not commented out also there is no harm in it

while starting the replicate if this kind of error appear's then we need to increase the discard file size to hold all the record's

ERROR OGG-01172 Discard file (./dirrpt/TRANR1.DSC) exceeded max bytes (1000000).

INCREASING THE DISCARD FILE SIZE

Step1

Go to the particular parameter file and add to the below parameter in the file

Here we are transferring the data two source table's to two target table's

Check the report file you can view this king of error message in it

2012-08-26 18:04:22 ERROR OGG-01172 Discard file (./dirrpt/TRANR1.DSC) exceeded max bytes (1000000).

***********************************************************************

* ** Run Time Statistics ** *

***********************************************************************

Reading ./dirdat/t1000150, current RBA 1325874, 37 records

Report at 2012-08-26 18:04:22 (activity since 2012-08-26 18:04:21)

From Table <source_table>to <target_table>: -- table 1 from source and target

# inserts: 0

# updates: 0

# deletes: 0

# discards: 275

From Table <source_table>to <target_table>:-- table 2 from source and target

# inserts: 37

# updates: 0

# deletes: 0

# discards: 0

Stored procedure fusion.gl_remote_transfer_pkg.do_import:

attempts: 37

successful: 37

From Table <source_table>to <target_table>:

Stored procedure tt3:

attempts: 37

successful: 37

Adding the discard file with the specific value

DISCARDFILE ./dirrpt/TRANR1.DSC, APPEND, MEGABYTES 100

DISCARDFILE -keyword
./dirrpt/TRANR1.DSC -File location
APPEND - it will append the discard file when the discard file contains already data in it
MEGABYTES <value> -estimate the volume of the duplicate data and according to ti we should give the size if you want to
Size in GB you have to specify the Parameter GIGABYTE [GB]

Adding the discard file with the PURGE

DISCARDFILE ./dirrpt/TRANR1.DSC, PURGE

if we add the discard file with the purge command then when ever you restart the replicate or extract the previous data which is residing in the  discard file will be purged
Both the parameter's can't be added at the same time .. we have to choose nay one of the option's

Step 2

Start the replicate ...

Check the report file for how many discard's had happened

Reading ./dirdat/t1000151, current RBA 2111708, 2183 records

Report at 2012-08-26 23:27:51 (activity since 2012-08-26 18:09:41)

From Table <source_table>to <target_table>: -- table 1 from source and target
# inserts: 2133
# updates: 0
# deletes: 0
# discards: 364
From Table  <source_table>to <target_table>:-- table 2 from source and target
# inserts: 82
# updates: 0
# deletes: 0
# discards: 0
Stored procedure fusion.gl_remote_transfer_pkg.do_import:
attempts: 125
successful: 125

From Table GL.GL_XFR_TRACKING to FUSION.GL_XFR_TRACKING:

Stored procedure tt3:
attempts: 125
successful: 125

Now check the discard file which is created on the  location which have been specified in the parameter

[oracle@fahdb dirrpt]$ ll *.DSC

-rw-r--r-- 1 oracle oinstall 3642373 Aug 26 23:33 TRANR1.DSC

Monday, August 20, 2012

Applying PSU Patch on the grid ASM and db with oracle restart before Upgrade to 11.2.0. 3

Applying the PSU Patchs on the grid ASM and db with oracle restart environment before starting the Upgrade

Here we upgrade the 11.2.0.2 grid infrastructure ASM with oracle restart and database to 11.2 .0.3

Before starting the upgrade we need to apply the PSU[patch set update] patches on the grid home and the oracle home for applying the PSU patches we need the latest OPatch .. we can download the latest OPatch from the MOS

we can download the p6880880_112000_Linux-x86-64.zip for the OPatch from the MOS

Upgrading the OPatch with the latest version of OPatch available from MOS

Step1

Backup the $ORACLE_HOME/OPatch in to the new directory OPatch_bkp

cp -r OPatch/ OPatch_bkp

[oracle@fahdb dbhome_1]$ ll OP*

OPatch:

total 140

drwxr-xr-x 3 oracle oinstall 4096 Aug 20 00:55 crs

drwxr-xr-x 2 oracle oinstall 4096 Aug 20 00:55 docs

-rw-rw-r-- 1 oracle oinstall 23695 Mar 21 23:24 emdpatch.pl

drwxr-xr-x 2 oracle oinstall 4096 Feb 20 21:58 fmw

drwxr-xr-x 2 oracle oinstall 4096 Aug 20 00:55 jlib

drwxr-xr-x 5 oracle oinstall 4096 Aug 20 00:55 ocm

-rwx--x--- 1 oracle oinstall 31471 Mar 21 23:24 opatch

-rwxrwxr-x 1 oracle oinstall 18425 Mar 21 23:24 opatch.bat

-rwxrwxr-x 1 oracle oinstall 10056 Mar 21 23:24 opatchdiag

-rwxrwxr-x 1 oracle oinstall 9352 Mar 21 23:24 opatchdiag.bat

-rw-rw-r-- 1 oracle oinstall 49 Mar 21 23:24 opatch.ini

-rw-rw-r-- 1 oracle oinstall 2576 Mar 21 23:24 opatch.pl

drwxr-xr-x 4 oracle oinstall 4096 Aug 20 00:55 opatchprereqs

drwxrwxr-x 3 oracle oinstall 4096 Mar 21 23:25 oplan

-rw-rw-r-- 1 oracle oinstall 2913 Mar 21 23:24 README.txt

OPatch_bkp:

total 80

drwxr-xr-x 3 oracle oinstall 4096 Aug 20 00:54 crs

drwxr-xr-x 2 oracle oinstall 4096 Aug 20 00:54 docs

-rw-r--r-- 1 oracle oinstall 23695 Aug 20 00:54 emdpatch.pl

drwxr-xr-x 2 oracle oinstall 4096 Aug 20 00:54 fmw

drwxr-xr-x 2 oracle oinstall 4096 Aug 20 00:54 jlib

drwxr-xr-x 2 oracle oinstall 4096 Aug 20 00:54 ocm

-rwxr-xr-x 1 oracle oinstall 22150 Aug 20 00:54 opatch

-rw-r--r-- 1 oracle oinstall 49 Aug 20 00:54 opatch.ini

-rw-r--r-- 1 oracle oinstall 2590 Aug 20 00:54 opatch.pl

drwxr-xr-x 4 oracle oinstall 4096 Aug 20 00:54 opatchprereqs

Step2

And remove the contents from the OPatch directory and

cd $ORACLE_HOME/OPatch

rm -rf *

Step3

unzip the p6880880_112000_Linux-x86-64.zip in the oracle home and the grid home where we need the latest version of the OPatch

make sure you are in the ORACLE_HOME and the unzip the OPatch

unzip /home/oracle/p6880880_112000_Linux-x86-64.zip

Step4

Check the verion of the OPatch

[oracle@fahdb ~]$ /u01/app/oracle/oracle/product/11.2.0/dbhome_1/OPatch/opatch version

OPatch Version: 11.2.0.3.0

OPatch succeeded.

NOTE:

The above mentioned steps are normal process of upgrading the Opatch please read the latest patch README according to nay specific change for that patch

Creating the OCM Response file [ocm.rsp]

Step 1
we need to create the response file for the oracle configuration manager if you have installed on your system

Go to the Opatch directory and then find the ocm/bin

[oracle@fahdb bin]$ pwd
/u01/app/oracle/oracle/product/11.2.0/dbhome_1/OPatch/ocm/bin

[oracle@fahdb bin]$ ls
emocmrsp

Step2

Run the emocmrsp to generate a new response file

[oracle@fahdb bin]$ ./emocmrsp

OCM Installation Response Generator 10.3.4.0.0 - Production

Provide your email address to be informed of security issues, install and initiate Oracle Configuration Manager. Easier for you if you use your My Oracle Support Email address/User Name. Visit http://www.oracle.com/support/policies.html for details. Email address/User Name: bpalaneandavar@a-bits.biz

Password (optional):

The OCM configuration responsefile (ocm.rsp) was successfully created

Step3
Check the File has been created on the same location
[oracle@fahdb bin]$ ll
total 16
-rwxrw---- 1 oracle oinstall 9063 Nov 27 2009 emocmrsp
-rw-r--r-- 1 oracle oinstall 2969 Aug 20 11:45 ocm.rsp

NOTE:
we can use the same response file for different patchs if you MOS details are changed then you can proceed with creating the new ocm.rsp file

Applying the PSU patches according the version we have the source as 11.2.0. 2 and to be upgraded to 11.2.0.3

we are applying the patch on 11.2.0.2 home [both the grid and the oracle home] we are applying the patch 12539000 as the pre reqiust

For grid apply the patch as the root

Check the oracle HAS is running in the system if not the patch will fail HAS should be up and running for applying the patch
any database which is using the ASM should be shutdown The LISTENER,ASM,CRS shoud be up for applying the patch

[root@fahdb 12539000]# /u01/app/oracle/grid/11.2.0/grid/OPatch/opatch auto /home/grid/12539000/ -oh /u01/app/oracle/grid/11.2.0/grid/
Executing /usr/bin/perl /u01/app/oracle/grid/11.2.0/grid/OPatch/crs/patch112.pl -patchdir /home/grid -patchn 12539000 -oh /u01/app/oracle/grid/11.2.0/grid/ -paramfile /u01/app/oracle/grid/11.2.0/grid/crs/install/crsconfig_params
opatch auto log file location is /u01/app/oracle/grid/11.2.0/grid/OPatch/crs/../../cfgtoollogs/opatchauto2012-08-20_00-27-44.log
Detected Oracle Restart install
Using configuration parameter file: /u01/app/oracle/grid/11.2.0/grid/crs/install/crsconfig_params
OPatch is bundled with OCM, Enter the absolute OCM response file path:
/u01/app/oracle/grid/11.2.0/grid/OPatch/ocm/bin/ocm.rsp
Enter 'yes' if you have unzipped this patch to an empty directory to proceed (yes/no):yes
Clusterware is either not running or not configured. You have the following 2 options
1. Configure and Start the Clusterware on this node and re-run the tool
2. or Run the tool with the -och <CRS_HOME_PATH> option and then invoke tool with -oh <comma seperated ORACLE_HOME_LIST> to patch the RDBMS home

[grid@fahdb ~]$ crsctl start has

CRS-4123: Oracle High Availability Services has been started.

[grid@fahdb ~]$ crsctl status resource -t

--------------------------------------------------------------------------------

NAME TARGET STATE SERVER STATE_DETAILS

--------------------------------------------------------------------------------

Local Resources

--------------------------------------------------------------------------------

ora.DATA.dg

ONLINE ONLINE fahdb

ora.FLASH.dg

ONLINE ONLINE fahdb

ora.LISTENER.lsnr

ONLINE ONLINE fahdb

ora.asm

ONLINE ONLINE fahdb Started

ora.ons

OFFLINE OFFLINE fahdb

--------------------------------------------------------------------------------

Cluster Resources

--------------------------------------------------------------------------------

ora.cssd

1 ONLINE ONLINE fahdb

ora.diskmon

1 ONLINE ONLINE fahdb

ora.evmd

1 ONLINE ONLINE fahdb

ora.fahdb.db

1 OFFLINE OFFLINE

[root@fahdb 12539000]# /u01/app/oracle/grid/11.2.0/grid/OPatch/opatch auto /home/grid/12539000/ -oh /u01/app/oracle/grid/11.2.0/grid/

Executing /usr/bin/perl /u01/app/oracle/grid/11.2.0/grid/OPatch/crs/patch112.pl -patchdir /home/grid -patchn 12539000 -oh /u01/app/oracle/grid/11.2.0/grid/ -paramfile /u01/app/oracle/grid/11.2.0/grid/crs/install/crsconfig_params

opatch auto log file location is /u01/app/oracle/grid/11.2.0/grid/OPatch/crs/../../cfgtoollogs/opatchauto2012-08-20_00-56-16.log

Detected Oracle Restart install

Using configuration parameter file: /u01/app/oracle/grid/11.2.0/grid/crs/install/crsconfig_params

OPatch is bundled with OCM, Enter the absolute OCM response file path:

/u01/app/oracle/grid/11.2.0/grid/OPatch/ocm/bin/ocm.rsp

Enter 'yes' if you have unzipped this patch to an empty directory to proceed (yes/no):yes

The opatch minimum version check for patch /home/grid/12539000/etc failed for /u01/app/oracle/grid/11.2.0/grid

The opatch minimum version check for patch /home/grid/12539000/files failed for /u01/app/oracle/grid/11.2.0/grid

Opatch version check failed for oracle home /u01/app/oracle/grid/11.2.0/grid

Opatch version check failed

update the opatch version for the failed homes and retry

Check the version of the opatch

[root@fahdb 12539000]# /u01/app/oracle/grid/11.2.0/grid/OPatch/o

ocm/ opatch opatch.bat opatchdiag opatchdiag.bat opatchprereqs/ oplan/

[root@fahdb 12539000]# /u01/app/oracle/grid/11.2.0/grid/OPatch/opatch version

OPatch Version: 11.2.0.3.0

OPatch succeeded.

As the patch need the version higher that the 11.2.0.1 we are with the with the latest version the the patch fails then we need apply the patch manually

Steps for applying the Patch 12539000 manually

Unlock the grid from the root

[root@fahdb grid]# cd crs/install/

[root@fahdb install]# ls

cmdllroot.sh crsconfig_params crspatch.pm install.excl onsconfig preupdate.sh rootofs.sh s_crsconfig_lib.pm

crsconfig_addparams.sbs crsconfig_params.sbs hasdconfig.pl install.incl oracss.pm rootcrs.pl s_crsconfig_defs

crsconfig_lib.pm crsdelete.pm inittab installRemove.excl paramfile.crs roothas.pl s_crsconfig_fahdb_env.txt

[root@fahdb install]# ./roothas.pl -unlock

Using configuration parameter file: ./crsconfig_params

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'fahdb'

CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'fahdb'

CRS-2673: Attempting to stop 'ora.DATA.dg' on 'fahdb'

CRS-2673: Attempting to stop 'ora.FLASH.dg' on 'fahdb'

CRS-2673: Attempting to stop 'ora.evmd' on 'fahdb'

CRS-2677: Stop of 'ora.FLASH.dg' on 'fahdb' succeeded

CRS-2677: Stop of 'ora.DATA.dg' on 'fahdb' succeeded

CRS-2673: Attempting to stop 'ora.asm' on 'fahdb'

CRS-2677: Stop of 'ora.asm' on 'fahdb' succeeded

CRS-2673: Attempting to stop 'ora.cssd' on 'fahdb'

CRS-2677: Stop of 'ora.LISTENER.lsnr' on 'fahdb' succeeded

CRS-2677: Stop of 'ora.cssd' on 'fahdb' succeeded

CRS-2673: Attempting to stop 'ora.diskmon' on 'fahdb'

CRS-2677: Stop of 'ora.evmd' on 'fahdb' succeeded

CRS-2677: Stop of 'ora.diskmon' on 'fahdb' succeeded

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'fahdb' has completed

CRS-4133: Oracle High Availability Services has been stopped.

Successfully unlock /u01/app/oracle/grid/11.2.0/grid

When you unlock it it will bring down Oracle has[crs]

$ORACLE_HOME/OPatch/opatch apply -oh <the oracle home to be patched> -local <patch dir>

[grid@fahdb 12539000]$ /u01/app/oracle/grid/11.2.0/grid/OPatch/opatch napply -oh /u01/app/oracle/grid/11.2.0/grid -local /home/oracle/12539000

Oracle Interim Patch Installer version 11.2.0.3.0

Central Inventory : /u01/app/oracle/oraInventory

from : /u01/app/oracle/grid/11.2.0/grid/oraInst.loc

OPatch version : 11.2.0.3.0

OUI version : 11.2.0.2.0

Log file location : /u01/app/oracle/grid/11.2.0/grid/cfgtoollogs/opatch/opatch2012-08-20_02-03-58AM_1.log Verifying environment and performing prerequisite checks...

OPatch continues with these patches: 12539000

Do you want to proceed? [y|n]

User Responded with: Y

All checks passed.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/u01/app/oracle/grid/11.2.0/grid')

Is the local system ready for patching? [y|n]

User Responded with: Y

Backing up files...

Applying interim patch '12539000' to OH '/u01/app/oracle/grid/11.2.0/grid'

Patching component oracle.rdbms, 11.2.0.2.0...

Verifying the update...

Patch 12539000 successfully applied.

Log file location: /u01/app/oracle/grid/11.2.0/grid/cfgtoollogs/opatch/opatch2012-08-20_02-03-58AM_1.log

OPatch succeeded.

[grid@fahdb 12539000]$

[oracle@fahdb ~]$ /u01/app/oracle/oracle/product/11.2.0/dbhome_1/OPatch/opatch napply -oh /u01/app/oracle/oracle/product/11.2.0/dbhome_1 -local /home/oracle/12539000

Oracle Interim Patch Installer version 11.2.0.3.0

Oracle Home : /u01/app/oracle/oracle/product/11.2.0/dbhome_1

Central Inventory : /u01/app/oracle/oraInventory

from : /u01/app/oracle/oracle/product/11.2.0/dbhome_1/oraInst.loc

OPatch version : 11.2.0.3.0

OUI version : 11.2.0.2.0

Log file location : /u01/app/oracle/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/opatch2012-08-20_02-09-37AM_1.log

Verifying environment and performing prerequisite checks...

OPatch continues with these patches: 12539000

Do you want to proceed? [y|n]

User Responded with: Y

All checks passed.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/u01/app/oracle/oracle/product/11.2.0/dbhome_1')

Is the local system ready for patching? [y|n]

User Responded with: Y

Backing up files...

Applying interim patch '12539000' to OH '/u01/app/oracle/oracle/product/11.2.0/dbhome_1'

Patching component oracle.rdbms, 11.2.0.2.0...

Verifying the update...

Patch 12539000 successfully applied.

Log file location: /u01/app/oracle/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/opatch2012-08-20_02-09-37AM_1.log

OPatch succeeded.

[oracle@fahdb ~]$

Now we had applied the patch in oracle home and the grid home successfully again we have to lock the roor user by running the scripts

For database

As the root user we need to lock the rdbms first by running the rootadd_rdbms.sh

move to the directory rdbms install and you can find the script

cd /u01/app/oracle/grid/11.2.0/grid/rdbms/nstall

[root@fahdb install]# ls

config_filemap.sbs filemap.ora install.excl rdbms rootadd_filemap.sh rootadd_rdbms.sh sbs

[root@fahdb install]# ./rootadd_rdbms.sh

For Grid

[root@fahdb install]# pwd

/u01/app/oracle/grid/11.2.0/grid/crs/install

[root@fahdb install]# ls

cmdllroot.sh crsconfig_params crspatch.pm install.excl onsconfig preupdate.sh rootofs.sh s_crsconfig_lib.pm crsconfig_addparams.sbs crsconfig_params.sbs hasdconfig.pl install.incl oracss.pm rootcrs.pl s_crsconfig_defs crsconfig_lib.pm crsdelete.pm inittab installRemove.excl paramfile.crs roothas.pl s_crsconfig_fahdb_env.txt

[root@fahdb install]# ./roothas.pl -patch

Using configuration parameter file: ./crsconfig_params

Undefined subroutine &main::read_file called at crspatch.pm line 86

Error Undefined subroutine &main::read_file

roothas.pl -patch or rootcrs.pl -patch Fails with 'Undefined subroutine' [ID 1268390.1

Step 1

we need to run scrip with the below syntax the perl version which is used by the script is the wrong one so we need to run the script with the blow syntax

$<GRID_HOME>/perl/bin/perl -I$<GRID_HOME>/perl/lib -I$<GRID_HOME>/crs/install $<GRID_HOME>/crs/install/roothas.pl -patch

[root@fahdb install]# which perl

/usr/bin/perl

[root@fahdb install]# /u01/app/oracle/grid/11.2.0/grid/perl/bin/perl -l /u01/app/oracle/grid/11.2.0/grid/perl/lib -l /u01/app/oracle/grid/11.2.0/grid/crs/install/ /u01/app/oracle/grid/11.2.0/grid/crs/install/roothas.pl -patch

Step 2

[root@fahdb install]$ cp crsconfig_lib.pm crsconfig_lib_bkp.pm

[root@fahdb install]$ ls

cmdllroot.sh crsconfig_lib.pm crsdelete.pm inittab installRemove.excl paramfile.crs roothas.pl s_crsconfig_fahdb_env.txt

crsconfig_addparams.sbs crsconfig_params crspatch.pm install.excl onsconfig preupdate.sh rootofs.sh s_crsconfig_lib.pm

crsconfig_lib_bkp.pm crsconfig_params.sbs hasdconfig.pl install.incl oracss.pm rootcrs.pl s_crsconfig_defs

[grid@fahdb install]$ vi crsconfig_lib.pm

change the line From @exp_func = qw(check_CRSConfig validate_olrconfig validateOCR

To @exp_func = qw(check_CRSConfig validate_olrconfig validateOCR read_file

Step3

Re run the script now

[root@fahdb install]# ./roothas.pl -patch

Using configuration parameter file: ./crsconfig_params

ACFS-9200: Supported

CRS-4123: Oracle High Availability Services has been started.

Now the environment is ready for the upgrading the grid Home

show parameter memory_max_target which can be upto 1536M for the safer side