|
Oracle makes the following recommendation for which patch method to use for Database related installations:
- Every customer should at least install PSUs. Minimal testing required.
- 12.1.0.2 Customers wanting a more comprehensive set of fixes should install the Database Proactive Bundle patch. This requires a bit more testing than a Patch Set Update (PSU),but delivers a larger set of fixes.
- Since SPARC SuperCluster is an Engineered System that includes Exadata Storage Cells,SPARC SuperCluster follows a similar patch method to Exadata.
?
|
RELEASE
PLATFORM
Exadata
Exadata?
(when patching just Database and Grid Infrastructure)
All non-Exadata (RAC)
All non-Exadata (non-RAC)
Windows
12.1.0.2
Quarterly Full Stack Download Patch for Exadata?
Database Proactive Bundle Patch?1
Database Proactive Bundle Patch?1
Database Proactive Bundle Patch?1
Windows Database Bundle Patch
12.1.0.1
Database Grid Infrastructure PSU
Database Grid Infrastructure PSU?
(GI PSU)
Database PSU
11.2.0.4 and earlier
Database Patch for Exadata
Database Grid Infrastructure PSU?
(GI PSU)
Database PSU
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.
（编辑：广西网）
【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容!
