| | ## Applies to:
Oracle Database – Enterprise Edition – Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Information in this document applies to any platform.
Purpose
Patch Set Updates (PSUs) are proactive cumulative patches containing recommended bug fixes that are released on a regular and predictable schedule.
Details
Patch Set Updates (PSUs) for Oracle Products
My Oracle Support Note: 854428.1
January 15, 2013
Patch Set Updates (PSUs) are proactive cumulative patches containing recommended bug fixes that are released on a regular and predictable schedule. PSUs are on the same quarterly schedule as the Critical Patch Updates (CPU). Please see the "Critical Patch Updates" link on the Oracle Technical Network page for details and a schedule forcast.
The PSUs serve as a new baseline version for reporting issues to Oracle.
The following sections explain PSUs in greater detail:
– Section 1, "Oracle Products with Patch Set Updates"
– Section 2, "Patch Set Updates Overview"
– Section 3, "Patch Set Updates Lifecycle"
– Section 4, "Patch Set Update Availability"
– Section 5, "Patch Set Updates and Patch Conflict Resolution"
– Section 6, "Patch Set Updates and One-off Patches"
– Section 7, "Determining the Patch Set Update Version"
– Section 8, "On Request Patch Set Updates"
– Section 9, "Database Patch Set Updates"
– Section 10, "Exalogic Patch Set Updates"
– Section 12, "Documentation Accessibility"
1 Oracle Products with Patch Set Updates
Patch Set Updates (PSUs) are available for the following products:
– Oracle Database
– Oracle Grid Infrastructure
– Cluster Ready Services
– Enterprise Manager
– WebLogic Server
– Exalogic
2 Patch Set Updates Overview
Patch Set Updates (PSUs) offer the following features and benefits:
– Low-Risk, High-Value Content
– One Integrated, Well Tested Patch
– Baseline Version for Easier Tracking
2.1 Low-Risk, High-Value Content
PSU patches are intended to be low-risk. This is accomplished by controlling content and thorough testing. Bug fix inclusion criteria include the following:
– Critical technical issues with fixes that may affect a large number of customers and that are already proven in the field
– Critical Patch Update fixes
PSU patches do not include any of the following:
– Changes that require re-certification (for example, Database fixes that cause optimizer plan changes)
– Fixes that require configuration changes
Each PSU has limited new content, typically ranging from 25 to 100 new bug fixes. Content is selected from a review of patches with high customer downloads and critical issues that have been addressed by Development and Support. There is no direct request process for customers.
Database PSU patches are guaranteed to be rolling RAC installable.
2.2 One Integrated, Well Tested Patch
By including the recommended fixes in one patch, Oracle is able to ensure that the fixes work well together. Product regression tests are performed, and where appropriate stress, interoperability, and bug verification tests are also performed. Depending on the product, additional testing is performed for the PSU.
2.3 Baseline Version for Easier Tracking
Oracle associates a version number to the patch. The fifth number of the database version is incremented for each PSU. For example, the initial PSU is version 11.1.0.7.1, the second PSU for Release 11.1.0.7 is 11.1.0.7.2, and so on.
This enables customers and Oracle Support to refer to just one number, the version, rather than a list of one-off patches or sets of bundles that have been applied.
Any new one-off patches are requested on the five-number version number.
3 Patch Set Updates Lifecycle
A primary goal of the PSU program is to provide a series of proactive, stabilizing cumulative patches for a product version (release or patch set). The following are guidelines that Oracle follows for the PSU lifecycle for a product version. The specifics will vary depending on the content of individual PSUs.
– Once a patch set or release is available, the first PSU may occur as early as the next PSU cycle, or more typically at the second PSU cycle after the release. The timing is a function of both the targeted content and when in the quarterly period the release was made available.
– PSUs with security content will continue as long as the version is supported for CPU patches. The policies are outlined in Document 209768.1 Database, FMW, EM, and OCS Software Error Correction Support Policy.
– PSUs will reach a plateau of non-security content as the version stabilizes. Once this is reached, there will be a tapering off of non-security content. Oracle expects this plateau to be reached with the third or fourth PSU.
– PSU content will be primarily security-related once the next patch set in the series is released.
- PSUs with security content may be the only primary mechanism for CPU patching for certain products. Security content made available as part of the PSU may not available as Interim Patches and customers are recommended to install the latest available PSUs.
4 Patch Set Update Availability
The latest available PSUs are listed in the My Oracle Support notes indicated in Table 1. Table 1 Latest Available PSUs by Product Listed on My Oracle Support
| Product | My Oracle Support Note |
|---|
Database
Enterprise Manager
WebLogic Server
Oracle Elastic Exalogic Cloud Software
To find all currently recommended PSUs, one-off patches, and patch bundles, use the Patch Recommendations feature on the Patches & Updates tab in My Oracle Support.
5 Patch Set Updates and Patch Conflict Resolution
The PSU patches are packaged as one cumulative patch. The PSU can coexist with any one-off patch that does not conflict with it.
When a one-off patch conflicts with the PSU, patch conflict resolution is achieved by providing a one-off patch of that fix or set of fixes that coexists with the PSU patch. This is accomplished with a prerequisite/overlay patch. The new one-off patch requires that the PSU be present in the Oracle Home. It cannot be applied if the PSU is not first applied. That is, the PSU is a prerequisite of the one-off patch. At apply time, instead of rolling back the conflicting PSU patch, OPatch installs the one-off patch's files. That is, the one-off patch overlays the PSU. Prerequisite/overlay patches have the same 5-number version as the PSU.
The fastest and easiest way to determine whether you have one-off patches in the Oracle home that conflict with the PSU, and to get the necessary conflict resolution patches, is to use the Patch Recommendations and Patch Plans features on the Patches & Updates tab in My Oracle Support. These features work in conjunction with the My Oracle Support Configuration Manager. Recorded training sessions on these features can be found in Document 603505.1. Alternately, there are instructions in the PSU README for determining what patches are needed.
Oracle strives to provide quick turnaround and availability of Database conflict resolution patches by doing the following:
– At release time, providing new PSU conflict resolution patches for any overlay patches provided on the previous two PSUs
– Automating patch generation
– Giving priority to new conflict resolution patch requests that are required to install the PSUs
Oracle Database 11.2.0.1.2 is used in the following examples; however, the fundamental information is also pertinent to the other Patch Set Update patches.
– Example 1: Patches P1, P2, and P3 are installed in a Database 11.2.0.1.0 Oracle Home and patch P1 conflicts with PSU 11.2.0.1.2.
1. Before the PSU is installed, the OPatch prereq command will indicate any existing patches that conflict with the PSU. With this example, OPatch reports P1 as conflicting with the PSU.
2. Request a 11.2.0.1.2 one-off patch of P1.
- Rollback Patch P1
4. Apply PSU 11.2.0.1.2. Patches P2 and P3 will remain installed.
5. Apply the 11.2.0.1.2 prerequisite/overlay patch of P1.
– Example 2: Patches P4 and P5 are installed in a Database 11.2.0.1.0 Oracle Home, and both Patch P4 and P5 conflict with PSU 11.2.0.1.2.
1. Before the PSU is installed, the OPatch prereq command will indicate any existing patches that conflict with the PSU. With this example, OPatch reports P4 and P5 as conflicting with the PS.
2. Request a 11.2.0.1.2 one-off patch of P4 and a 11.2.0.1.2 one-off patch of P5.
- Rollback patches P4 and P5.
4. Apply PSU 11.2.0.1.2.
5. Apply the 11.2.0.1.2 prerequisite/overlay patches of P4 and P5.
– Example 3: Patches P4 and P5 from Example 2 are installed in a Database 11.2.0.1.1 Oracle Home, in preparation for installing PSU 11.2.0.1.2.
1. Before the PSU is installed, the OPatch prereq command will indicate any existing patches that conflict with the PSU. With this example, OPatch reports P4 and P5 as conflicting with the PSU.
2. Check if the 11.2.0.1.2 versions of P4 and P5 are available. If they are not available, request a 11.2.0.1.2 one-off patch of P4 and a 11.2.0.1.2 one-off patch of P5.
- Rollback patches P4 and P5.
4. Apply PSU 11.2.0.1.2.
5. Apply the 11.2.0.1.2 versions of patches P4 and P5.
6 Patch Set Updates and One-off Patches
There is no requirement to move to the latest PSU to get a one-off patch of a bug fix. Oracle provides one-off fixes on all PSU versions as long as the release or patch set version is supported for error correction.
Once a patch set update is applied, service requests for new problems and new one-off patch requests are filed on the current 5-number PSU version installed.
– Example 1: PSU 11.2.0.1.2 is installed, and bug 123456 is encountered.
If an 11.2.0.1.0 patch exists for bug 123456 and it does not conflict with the PSU or if there is an existing 11.2.0.1.2 patch, then apply it.
Otherwise, do the following:
1. Request a one-off patch for 123456 on top of 11.2.0.1.2.
2. Apply the one-off patch after Oracle provides it.
7 Determining the Patch Set Update Version
Patch Set Updates are referenced by their 5-place version number. The following OPatch commands are a simple way to determine the latest PSU installed in the Oracle Home.
For Database PSUs 11.2.0.3 and later, enter the following command: opatch lsinventory A list of all interim patches is returned. The PSU will display something like: Patch 20299017 : applied on Thu Apr 09 20:05:21 GMT 2015 Unique Patch ID: 18606652 Patch description: "Database Patch Set Update : 11.2.0.3.14 (20299017)"
Created on 8 Mar 2015, 07:19:52 hrs PST8PDTSub-patch 19769496; "Database Patch Set Update : 11.2.0.3.13 (19769496)" Sub-patch 19121548; "Database Patch Set Update : 11.2.0.3.12 (19121548)" Sub-patch 18522512; "Database Patch Set Update : 11.2.0.3.11 (18522512)" Sub-patch 18031683; "Database Patch Set Update : 11.2.0.3.10 (18031683)" Sub-patch 17540582; "Database Patch Set Update : 11.2.0.3.9 (17540582)" Sub-patch 16902043; "Database Patch Set Update : 11.2.0.3.8 (16902043)" Sub-patch 16619892; "Database Patch Set Update : 11.2.0.3.7 (16619892)" Sub-patch 16056266; "Database Patch Set Update : 11.2.0.3.6 (16056266)" Sub-patch 14727310; "Database Patch Set Update : 11.2.0.3.5 (14727310)" Sub-patch 14275605; "Database Patch Set Update : 11.2.0.3.4 (14275605)" Sub-patch 13923374; "Database Patch Set Update : 11.2.0.3.3 (13923374)" Sub-patch 13696216; "Database Patch Set Update : 11.2.0.3.2 (13696216)" Sub-patch 13343438; "Database Patch Set Update : 11.2.0.3.1 (13343438)"
Bugs fixed:
16929165, 14469008, 16710324, 14301592, 13834065, 16703112, 18436647For Database PSUs prior to 11.2.0.3, enter the following command:opatch lsinventory -bugs_fixed | egrep -i 'PSU|DATABASE PATCH SET UPDATE' A list will be output, and the highest release version reported is the current PSU installed. In the following example output, 11.2.0.2.6 is the installed Database PSU: 10248523 13696224 Fri Mar 30 14:00:25 EDT 2012 DATABASE PSU 11.2.0.2.1 11724916 13696224 Fri Mar 30 14:00:25 EDT 2012 DATABASE PSU 11.2.0.2.2 (INCLUDES CPUAPR2011) 12419331 13696224 Fri Mar 30 14:00:25 EDT 2012 DATABASE PSU 11.2.0.2.3 (INCLUDES CPUJUL2011) 12827726 13696224 Fri Mar 30 14:00:25 EDT 2012 DATABASE PSU 11.2.0.2.4 (INCLUDES CPUOCT2011) 13343424 13696224 Fri Mar 30 14:00:25 EDT 2012 DATABASE PATCH SET UPDATE 11.2.0.2.5 (INCLUDES CPUJAN2012) 13696224 13696224 Fri Mar 30 14:00:25 EDT 2012 DATABASE PATCH SET UPDATE 11.2.0.2.6 (INCLUDES CPUAPR2012) For CRS (Cluster Ready Services) PSUs, enter the following command: opatch lsinventory -bugs_fixed | grep -i 'TRACKING BUG' | grep -i 'PSU'For GI (Grid Infrastructure) PSUs, enter the following command: opatch lsinventory -bugs_fixed | grep -i 'GRID INFRASTRUCTURE PATCH SET UPDATE'
For Windows Users: In the following commands for Enterprise Manager PSUs, use findstr /i instead of grep -i.
For Enterprise Manager Agent PSUs, enter the following command: opatch lsinventory -bugs_fixed | grep -i 'ENTERPRISE MANAGER' | grep -i 'AGENT'For Enterprise Manager OMS PSUs, enter the following command: opatch lsinventory -bugs_fixed | grep -i 'ENTERPRISE MANAGER' | grep -i 'OMS'For WebLogic Server PSUs, enter the following commands, where WL_HOME is the path of the WebLogic home: $ . $WL_HOME/server/bin/SetWLSEnv.sh $ java weblogic.versionIn the following example output, 10.3.4.0.1 is the installed WebLogic Server PSU. WebLogic Server 10.3.4.0.1 PSU Patch for Bug11677325 Wed Feb 23 10:52:30 IST 2011 WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255
8 On Request Patch Set Updates
For platform-version combinations that have fewer than 10 downloads in the prior quarterly period, Oracle delivers Patch Set Updates for these historically inactive platform-version combinations only when requested.
To obtain a PSU for a platform-version combination that is available only by request, file a service request (SR) with Oracle Global Support. You may file an on-request PSU SR as long as the base release version is supported for error correction. Once the terminal PSU is released, you may file requests for two weeks after the terminal PSU is released.
You can make a request at any time, but you cannot request a specific PSU (such as 10.2.0.4.3). Either the current PSU or the next PSU will be provided, depending on when the request is received and processed. A planned availability date for the PSU will be provided in the service request.
Hint: There is no cutoff date when the NEXT PSU will be built instead of the CURRENT one. Generally development begins building the OR patches once the new release is complete as all resources are dedicated to building the new release. If the upcoming release is desired over the current release, it is suggested to file the request a week or so before the upcoming release is available.
9 Database Patch Set Updates
The following sections describe information that is only pertinent to Database Patch Set Updates:
– Section 9.1, "Patch Set Updates and Security Patch Updates (SPUs)"
– Section 9.2, "Grid Infrastructure (GI) Patch Set Update and Database Patch Set Update"
– Section 9.3, "Cluster Ready Services (CRS) Patch Set Update and Database Patch Set Update"
– Section 9.4, "Overlay Patch Set Updates"
9.1 Patch Set Updates and Security Patch Updates (SPUs)
The PSU and SPU patches released each quarter contain the same security content. Oracle recommends the PSU as it provides additional critical bug fixes. The SPU and PSU patches employ different patching mechanisms, so customers need to take into account the following information when selecting between Database SPUs and PSUs.
– A PSU can be applied on the SPU released at the same time or on any earlier SPU for the base release version. A PSU can be applied on any earlier PSU or the base release version. SPUs are only created on the base release version.
– Once a PSU has been installed, the recommended way to get future security content is to apply subsequent PSUs. Reverting from PSU back to SPU, while possible, would require significant effort, and so is not advised.
9.2 Grid Infrastructure (GI) Patch Set Update and Database Patch Set Update
GI PSU of a specific version always contains the Database PSU fixes of the same version. In such cases, the GI PSU patch should be applied to both the GI home and the Database home. For example, GI PSU 11.2.0.2.3 should be applied to both the GI home and the Database home. As of April 2012, guidance on Grid Infrastructure configurations and how to apply the GI and Database PSUs to them are in the GI PSU READMEs.
9.3 Cluster Ready Services (CRS) Patch Set Update and Database Patch Set Update
For the 11.1.0.7 and 10.2.0.4 Database releases, Oracle provides a Cluster Ready Services (CRS) PSU patch and a Database PSU patch. Both of these patches provide Oracle recommended bug fixes.
The CRS PSU can be applied to the CRS home, and the Database PSU can be applied to the ASM and Database homes.
Any combination of CRS PSU and Database PSU is supported.
9.4 Overlay Patch Set Updates
An overlay Patch Set Update is a patch that is installed on a base Patch Set Update patch. Oracle provides an overlay Patch Set Update when analysis of the contents shows that there are few conflicting one-off patches. This packaging eliminates the need for overlay one-off patches on the previous PSU to be replaced with new overlay one-off patches. When a customer has already installed the base Patch Set Update, then this results in a reduction in the time to apply the Patch Set Update and no wait for new overlay one-off patches.
The overlay Patch Set Update is cumulative from the time of the base Patch Set Update.
The conflict resolution for overlay Patch Set Updates is similar to the conflict resolution for two conflicting overlay patches. A merge overlay Patch Set Update is provided that contains the overlay PSU contents and the conflicting one-off patch fixes in one patch. The merge patch is installed instead of the overlay PSU.
If the base Patch Set Update is not yet installed, then it must be installed before you install the overlay Patch Set Update. The readme has instructions on how to install in this scenario.
Starting with PSU 10.2.0.4.5, all 10.2.0.4 PSUs are overlay PSUs with 10.2.0.4.4 as the base PSU. No other PSU versions will be released as overlay PSUs.
10 Exalogic Patch Set Updates
The Exalogic Patch Set Update is a single download of component patches that have been tested together. As the patch packaging is unique for PSUs, there are some variations to the above information:
– The Exalogic Patch Set Update does not have its own version number. Instead, it is referred to based on when it has been released. The first one is the Exalogic PSU for April 2011
– If there are patch conflicts between a component patch included in the Exalogic PSU and other patches for the component product, then the resolution follows the component's usual processing for patch conflict resolution. For example, if there are patch conflicts with the WebLogic Server PSU component patch in the Exalogic PSU, then the conflict resolution is as done for the WebLogic Server PSU.
11 References
Document 756388.1 Introduction to Oracle Recommended Patches
Document 1306505.1 Announcing Oracle WebLogic Server PSUs (Patch Set Updates)
Document 1314535.1 Announcing Exalogic PSUs (Patch Set Updates)
Document 305.1 Patching & Maintenance Advisor: Oracle Fusion Middleware (FMW) 11g
12 Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/us/corporate/accessibility/index.html. Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.
Patch Set Updates (PSUs) for Oracle Products
Copyright © 2006, 2013, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open Company, Ltd.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.