|
1?The "Database Proactive Bundle Patch" requires a bit more testing than a Patch Set Update (PSU) as it delivers a larger set of fixes.?
Additionally
- In all cases install the relevant OJVM PSU
- Install interim patches only for specific issues that you know will apply to your environment.
- Keep the number of interim patches installed to a minimum.
Database SPU is still available as a valid patching method for 11g releases - it is recommended to transition to PSU patching model.?
(SPU might be considered lowest change risk,but it leaves you exposed to critical issues fixed in the matching PSU).
Altering the Patching Method
If you wish to change between patching methods then you can do this when upgrading to a new Patch Set Release (PSU). To change patching methods whilst staying on the same Patch Set Release / 4 field version you typically need to:
- Fully rollback the current method patch/es
- This may need you to rollback some interim patches too – make a note of any interim patches rolled back
- Apply / install the new method patch/es to at least the same CPU cycle
- Acquire and apply any interim patches required to maintain the same fixes as were in place before
?
12.1.0.2 DBBP to 12.1.0.2 PSU
You cannot mix the?Database Proactive Bundle Patch?(DBBP) patching method and the DB PSU patching method in the same ORACLE_HOME.
eg: If you install?the DBBP?on a system,then you cannot subsequently install a later "Database PSU" (DB PSU) on top of that. You would need to stay on the DBBP path?OR?fully roll back all of the historical DBBP patches (iteratively - on at a time) and then apply DB PSU patches to switch patching methods.
Example:
?
12.1.0.2 PSU to 12.1.0.2 DBBP
Beginning in September 2018,Oracle now?supports?switching from the 12.1.0.2?"PSU" patching strategy to the 12.1.0.2 "DBBP" patching strategy simply by applying the latest quarterly "DBBP" patch using the latest version of the Opatch tool.? For assistance obtaining the newest version of the Opatch tool for Oracle 12.1.0.2 software,please refer to "OPatch - Where Can I Find the Latest Version of OPatch(6880880)?" [Video]Note 224346.1
?
11.2.0.4 PSU to 11.2.0.4 SPU or vice versa
It is not generally advisable to switch from "Database PSU" to "Database SPU" method.
?
Patch Conflict Resolution
If interim patches are used in conjunction with one of the proactive patching methods then there may be some patch conflicts.
For the quarterly proactive patches released as part of the Critical Patch Update program (DB PSU,Quarterly Database Patch for Exadata,and?Database Proactive Bundle Patch,Oracle proactively produces new interim patches for existing patches that would conflict. The new interim patches are usually released at the same time as the proactive bundles.
For information about resolving patch conflicts see the following documents:
-
Document:1941934.1?My Oracle Support Patch Conflict Checker Overview?[Video]
-
Document:1091294.1?How to Use the My Oracle Support Conflict Checker Tool for Patches Installed with OPatch [Video]
-
Document:1321267.1?Database Patch Conflict Resolution
Frequently Asked Questions (FAQ)
- Can I use "Quarterly Database Patch for Exadata" (11.2.0.x) on non-Exadata systems?
- No,Oracle does not support this.
- Most updates are delivered in bundle patches created specifically for Exadata for Oracle Database (DB_BP) and Oracle Clusterware (GI_BP).? Bundle patches contain no Exadata-specific code,however,they may only be installed on non-Exadata systems for testing purposes,or when providing disaster recovery support for an Exadata system.? Oracle will supply interim fixes on top of Exadata bundle patches for non-Exadata systems only when the non-Exadata system is being used in a Data Guard environment as the primary or standby system for an Exadata system.
- Can I use "Database Proactive Bundle Patch" (12.1.0.2+) on non-Exadata systems?
- Yes. This patch is applicable for non-Exadata systems.?
- The fix information for the bundle may include some "Exadata" specific fixes but that is because the bundle is also applicable to Exadata systems.?
- Please refer to?Note 1937782.1?12.1.0.2 Database Proactive Bundle Patches / Bundle Patches for Engineered Systems and DB In-Memory - List of Fixes in each Bundle - List of Fixes in each Bundle for more information.
- Do proactive patches include optimizer fixes?
- "Database SPU" and "Database PSU" do?not?include optimizer fixes
- "Database Patch for Exadata"?can?include optimizer fixes for wrong results issues,but only in a form that allows them to be individually enabled/disabled as required.
- "Windows Database Bundle Patch"?can?include optimizer fixes
- How can I tell what patching method an installation uses?
- Review the opatch lsinventory output to see what patches are applied.?
SPU,PSU and BP patches include a description of the patch name/version in the output.
- What is the difference between "Windows Database Bundle Patch" and "Database Patch for Exadata" etc.. ?
- These BP are targeted? at different environments. The latest versions will include the same SPU and PSU content,but all other content is specific to the target environment - there may be some other common content but there will be differences in content.
- Do proactive patches affect the database version as reported in tracefiles and database views like V$VERSION?
- No. The patch level is reflected in the opatch lsinventory data,and for some patch types is reflected in DBA_REGISTRY or DBA_REGISTRY_HISTORY
?
Current Database Proactive Patches
The following tables give information on currently available proactive database related patches,including some patch types that are no longer produced.
Proactive Database Patches by Platform / Environment / Version
Short names used in the "Method/s" column of the following table are expanded on in the next section.
| 