Product Compatibility: This book applies to all Database 12.x, Enterprise Manager 12c/13c, and Fusion Middleware 12.x releases. OPatch consists of patching utilities that help ensure your Oracle software stays current and secure. The utilities are:. OPatch: A Java-based utility that enables the application and rollback of patches to Oracle software.
![Opatch detects your platform as 23 while this patch lyrics Opatch detects your platform as 23 while this patch lyrics](/uploads/1/2/5/4/125425491/179151037.png)
OPatchauto: A patch orchestration tool that generates patching instructions specific to your target configuration and then uses OPatch to perform the patching operations without user intervention. Specifically, OPatchAuto can:. Perform pre-patch checks. Apply the patch. Start and stop the running servers.
Apr 22, 2011 - Contents. ArcSight ESM, Version 5.0 SP1 Patch 2. Download the Oracle 10g or 11g OPatch file for your platform.
Perform post-patch checks. Roll back patches when patch deinstallation is required. OPatchauto -binary: A patch application tool that applies a single patch on a selected Oracle home. OPatchauto -binary patches only one Oracle home per session. These utilities provide you with the flexibility to analyze, troubleshoot, and patch an individual GI (Grid Infrastructure)/RAC (Real Application Cluster) home environments.
For large-scale IT environments, patching individual product (e.g., Fusion Middleware) homes may not be practical since patching large numbers of targets manually is both monotonous and error prone. To maintain and deploy Oracle patches across many targets across your organization, you can use Enterprise Manager Cloud Control's patch automation capability. For more information about Enterprise Manager's patch management solution, see the 'Patching Software Deployments' in the. This chapter covers the following introductory and overview topics:. The patch process is not always straight forward as there are numerous factors that determine which software patches you need and how these patches should be applied.
For example, the types of Oracle software installed on each target, software versions, or platforms on which the software is running are just a few. 1.1.1 Obtaining the Patches You Need As shown in, the first step is to determine what patches you need. You may find out about required patches from blogs, Oracle Technology Network (OTN), Service Requests, Knowledge Articles, Oracle documentation, or any number of other sources. However, the single source of truth for patching is the Oracle Support Web site—My Oracle Support (MOS). From here, you have access to interactive support tools and information that simplify searching for and obtaining the requisite patches for your Oracle environment. You can find complete documentation about MOS at the following location. Figure 1-3 MOS Patches and Updates From this page, you can search for the desired patch based on a specific configuration.
One particularly useful search feature is the Recommended Patch Advisor. The Recommended Patch Advisor lets you find recommended and mandatory patches for standalone products, product combinations, or products for a product stack. For example, using the Recommended Patch Advisor, you search for patches for the following product:.
Product: Oracle Database. Release: 11.2.0.2.0. Platform: Linux x86-64 This search returns the following results: By clicking on patch 14727315 (PSU) you are taken to the patch page where you can view bugs resolved by this patch, related Knowledge Articles, or view a generic patch README. From this page, you also complete Step 2 of the patching workflow—Download the patch to your local system. The following list summarizes sources from which you can obtain patches.
Oracle Support Services: If you are working directly with an Oracle Support engineer, you may be provided with a diagnostic patch or an interim patch. My Oracle Support: As part of your regular patch maintenance schedule, you can obtain all patches from My Oracle Support: Once you log in, click the Patches & Updates tab to begin your patch search. My Oracle Support offers several patch download options and automated tools to help you keep current with patches. See the Patches & Updates Web-based help for more information:. Oracle Technology Network: Some Oracle software may be distributed through the Oracle Technology Network: Types of Oracle Patches Oracle regularly makes patches available to upgrade features, enhance security, or fix problems with supported software. 1.1.2.1 Manual Patching Using OPatch, you follow the generic instructions in the patch README.
You can view the patch README bundled with the patch or directly from the MOS page for the patch in question. You are required to read the linked support documentation and fill in the details of your specific configuration before you can implement any of the commands or add them to custom install scripts. Although this method is laborious, it provides you with a great deal of diagnostic capability and control if patch conflicts arise.
1.2 Patching with Enterprise Manager As useful as the OPatch utilities are, by themselves, they are limited in their ability to apply patches to large numbers of targets because they patch one GI/RAC home at a time. This could be challenging and time consuming in large, heterogeneous IT environments. In order to handle large-scale patching, Oracle provides a new patch management solution that integrates OPatch with Enterprise Manager Cloud Control 12 c. Enterprise Manager's tight integration with My Oracle Support (MOS) allows you to view patch recommendations, search patches, and roll out patches from a single user interface. In addition, Enterprise Manager's advanced Patch Plan feature provides you with a complete, end-to-end orchestration of the patching workflow. Automating the selection of deployment procedures and analysis of patch conflicts greatly reduces manual effort required to patch complex IT environments. Enterprise Manager integrates both OPatch and My Oracle Support for downloading and applying patches.
See the following documentation for information:. See 'Part VII: Patch Management' in the:. See the 'Patching Enterprise Manager' chapter in the:. Automation of patch conflict resolution and deployment through EM 12c.
1.5 OPatch Integration with Other Oracle Software In addition to Enterprise Manager, many Oracle software products have integrated the OPatch utilities to provide for a seamless and efficient patching task. Depending on the application, the call to the OPatch utility may be transparent, and all patching activity is maintained within the respective application.
These applications listed below have integrated OPatch into their respective environments. Always check the user documentation for any patching instructions before applying a patch. Fusion Middleware/Fusion Applications Other Oracle products, such as Fusion Middleware and Fusion Applications, integrate OPatch and may require different interaction to apply a particular patch. Refer to the following documentation:. For patching Fusion MiddleWare:. Section 2.3 'OPatch in a Fusion Middleware Environment' in the Oracle® Fusion Middleware Patching Guide:. Section 3 Applying the Latest Oracle Fusion Middleware Patch Set in the Oracle® Fusion Middleware Patching Guide:.
For patching Fusion Applications:. Section 3 Using Oracle Fusion Applications Patch Manager in the Oracle® Fusion Applications Patching Guide. 1.6 How to Access the OPatch Utilities With OPatch integrated in many Oracle products, the utility is automatically installed when you install the respective product (for example, Enterprise Manager). The patching tools are installed in the following directories:. OPatch - $ORACLEHOME/OPatch/opatch. OPatchAuto - $ORACLEHOME/opatch/opatchauto See and for a complete list of commands and options supported by OPatch utilities.
Scripting on this page enhances content navigation, but does not change the content in any way.
Scope: Enterprise Manager Grid Control - Version: 10.2.0.2 to 10.2.0.4 Sun Solaris SPARC (64-bit) Solaris Operating System (SPARC) (64-bit) Can effect any Opatch patching on Solaris SPARC 64 Bit Issue: While upgrading Enterprise Manager Grid Control 10.2.0.2 to 10.2.0.4, I faced an interesting issue which I later realized is, though not documented as one, a bug of the OPatch utility. As a prereq of the upgrade, one needs to apply the patch 4329444 to the repository database. But on applying the patch through the OPatch utility, the session fails with the message: Apply Session failed: ApplySession failed to prepare the system. OUI-67020:Interim Patch '4329444' is not applicable to OH '/oracle/grid/db10g'. Platforms not compatible OPatch detects Platform ID 453 while this patch supports the following platforms: 23: Sun SPARC Solaris (64-BIT)System intact, OPatch will not attempt to restore the system So here OPatch stops being smart, and fails to recognize the Platform ID correctly as 23 and instead it picks 453.
![Patch Patch](/uploads/1/2/5/4/125425491/136453021.gif)
Solution: Before running OPatch, set the OPATCHPLATFORMID environment variable to 23 by the following command export OPATCHPLATFORMID=23 And OPatch is smart again! Looks like it's been a long time, but great post; thanks for that info! In my case, the problem was on a Linux machine. The server is running RHEL5 64-bit.
The real issue there is that OPatch compares the Platform ID to the ARUID stored in $ORACLEHOME/inventory/ContentsXML/oraclehomeproperties.xml. On this server, that XML file contained the ARU designated for a 32-bit Linux system, not a 64-bit. I knew I had the right patch, so I just changed that env variable you pointed out here. Worked beautifully after that! I opened an SR with Oracle asking where that info comes from (because it obviously isn't from uname); haven't heard back from them yet.