介绍各种补丁集的使用方法：
Oracle Database - OvervIEw of Database Patch Delivery Methods - 12.1.0.2 and older (Doc ID 1962125.1)
APPLIES TO:Oracle Database - Enterprise Edition - Version 10.2.0.3 to 12.1.0.2 [Release 10.2 to 12.1]
Oracle Database - Standard Edition - Version 10.2.0.3 to 12.1.0.2 [Release 10.2 to 12.1]
Oracle Database - Personal Edition - Version 10.2.0.3 to 12.1.0.2 [Release 10.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
information in this document applIEs to any platform.
This document gives an overvIEw of the main patch delivery methods used for the Oracle Database.
It gives an overvIEw of the main characteristics of Patch Set Updates,Bundle Patches etc.. and explains which method applIEs to which environment.
ScopEThis document is intended for Oracle Database DBAs responsible for database software patching.
It gives an overvIEw of the varIoUs patch delivery methods that exist for patching on top of a database Base Release or Patch Set Release (PSR). It does not discuss about Base Releases nor Patch Set Releases,and only discusses the Oracle Database. It does not discuss Enterprise Manager.
DETAILS
Oracle Database - OvervIEw of Database Patch Delivery Methods - 12.1.0.2 and older (Doc ID 1962125.1) This NOTE covers Database Patch Delivery Methods for 12.1.0.2 and older versions. If you are interested in Methods for 12.2.0.1 and later versions,please see MOS Note 2337415.1.
Oracle Database - Overview of Database Patch Delivery Methods - 12.1.0.2 and older (Doc ID 1962125.1) Post Release Patch Delivery Methods Types of Proactive Patch (SPU / PSU / Bundle Patches) Version Numbers Testing Overview Testing Recommendation by Patch Type Which Patching Method to Use? Altering the Patching Method Patch Conflict Resolution Frequently Asked Questions (FAQ) Current Database Proactive Patches proactive Database Patches by Platform / Environment / Version More Information on Proactive Database Patches
Post Release Patch Delivery Methods
Oracle provIDes patches for both proactive and reactive maintenance:
Reactive Patches: are usually delivered as “Interim Patches” were historically kNown as “one-off” patches are provIDed on demand for a given “defect,version,platform” combination go through basic sanity tests fixes will usually be included in the next relevant Patch Set Release Each Patch Set has a "code freeze" date beyond which only "show-stopper" fixes are included. If a fix misses the the next Patch Set it will be included in the subsequent Patch Set (if there is one) Proactive Patches address high impact BUGs that affect a given configuration contain proven low risk fixes go through extra levels of testing,determined by the feature(s) affected are available on "My Oracle Support" by clicking on the "Patches & Updates" tabTypes of Proactive Patch (SPU / PSU / Bundle Patches)
There are different types of proactive patch available. This section gives a summary of the main proactive patching methods:
Security Patch Update (SPU) a cumulative collection of security fixes released as part of Oracle‘s Critical Patch Update (cpu) program delivered on pre-defined quarterly schedule Database SPU are always RAC Rolling and Standby First installable Note: Database SPUs are being phased out from Database Release 12c - cpu program security content will be delivered in the appropriate Bundle Patch or PSU (see below). Patch Set Update (PSU) a cumulative collection of fixes for proven high impact BUGs encountered in the fIEld includes the security fixes that are released as part of the cpu program guaranteed not to contain any changes to the optimizer or fixes which change application behavIoUr may span multiple stack componentsFor example: "Database GrID Infrastructure PSU" (GI PSU) includes fixes for both the GrID Infrastructure and the Database delivered on pre-defined quarterly schedule Database PSU and Database GrID Infrastructure PSU are always RAC Rolling and Standby First installable. OJVM PSU is neither RAC Rolling nor Standby First installable
Bundle Patch (BP) a cumulative collection of fixes to address BUGs in a given feature,product,or configuration
For example: windows Database Bundle Patch,Database Patch for Exadata, Database Proactive Bundle Patch a superset of PSU may span multiple stack components
For example: "Database Patch for Exadata" includes fixes both Database and GrID Infrastructure
delivered on pre-defined schedule,which may be more frequent than PSU releases are always RAC Rolling and Standby First installable As of April 2016,the Database Patch for Engineered Systems and Database In-Memory has been renamed to "Database Proactive Bundle Patch" "Quarterly Full Stack Download Patch" / "Combo Patch" delivers a number of different patches packaged together
For Example: "Quarterly Full Stack Download Patch for Exadata" includes "Quarterly Database Patch for Exadata" along with OJVM PSU and other Exadata system patches in a single download.
Other Proactive Patches Oracle produces some proactive patches for very specific purposes outsIDe of the normal SPU/PSU/BP cycle.
For example: special time-zone patches are released every 6 months for customers that require systems to use latest time-zone data
Such patches are usually delivered as "Interim Patches"
Database patch content for the varIoUs proactive patch methods might be visualized like this:
SPU contains only the cpu program security fixes PSU contains the cpu program security fixes and additional high-impact/low-risk critical BUG fixes BP includes all PSU fixes along with additional high value fixes
BP
PSU
SPU
An installation can only use one of the SPU,PSU or BP patching methods.
All methods allow “interim patches” to be installed,but the version of an interim patch required may vary depending on the patching method.
windows platforms are special in that they do not support normal “interim patches”.
See "More information on Proactive Database Patches" near the end of this document for details of current and historic proactive patches.
Version Numbers
The varIoUs patching methods have different ways to indicate the version as detailed in the following table:
| Term | Version Number | Example |
| Major Release | Designated by the first 2 fIElds of the version (fIElds are separated by decimal points) | 11.2 |
| Base Release | First 4 fIElds are the version of a Major Release | 11.2.0.1 |
| Patch Set Release (PSR) | Designated by the 4th fIEld of the version | 11.2.0.4 |
| Patch Set Update (PSU) | Designated by 5th fIEld of a version. | 11.2.0.4.160419 |
| Bundle Patch (BP) | Also designated by 5th fIEld of a version but with text to indicate which serIEs of bundle | Exadata Database Bundle Patch 11.2.0.4.160419 |
| Security Patch Update (SPU) | Designated by a month/year | 11.2.0.4 Jan 2015 SPU |
As of November 2015,the version numbering for new Bundle Patches,Patch Set Updates,and Security Patch Updates for Oracle Database have a new format. This new format replaces the numeric 5th fIEld of the bundle version with a release date in the form YYMMDD:
YY is the last 2 digits of the year
MM is the numeric month (2 digits)
DD is the numeric day of the month (2 digits)
Note that the release date is the release date of the main BP,PSU,or SPU.
This new version format makes it easIEr to see which bundle patches are from which time frame,and in particular,which patches are from the same Critical Patch Update release. For examples and more information,see My Oracle Support Note 2061926.1,Oracle Database,Enterprise Manager and MIDdleware - Change to Patch Numbering from Nov 2015 onwards.
Note:
Only the first 4 fIElds of a version are shown in Database vIEws / trace banners etc.. The 5th fIEld and patching method can be verifIEd by checking the inventory of an installation.
eg: "opatch lsinventory" will show the Patch Set (or Base Release) level along with a List of patches installed. The patch Listing usually shows a descriptive line/s for SPU/PSU/BP patches indicating what patch method and version is in use.
In earlIEr RDBMS Product versions (such as Oracle 8 and Oracle 9),this same version numbering system was referred to as "digits",as in "the version number 9.2.0.4 shows the Major Release is the first two digits of 9.2". Therefore,you may still find some legacy Oracle sources that refer to a version number such as 12.1.0.2,as "showing the Major Release is the first two digits of 12.1". Since "12.1" is technically 3 digits and *not* 2 digits,the term "fIEld" used in the table above is preferred over the legacy term "digit".
Testing OvervIEw
Oracle performs different types of testing on varIoUs patch types prior to their release:
Functional tests test specific areas of functionality against expected outcomes.An "area" may be a feature or subset of a feature (eg: Advanced @R_788_4403@ or a specific functionality of Advanced @R_788_4403@) functional tests include regression testing to ensure that results and behavIoUr of specific operations are as expected. Stress tests test resilIEnce of the database when pushed to its limit in resource utilization and in specific configurations heavy destructive tests under high load Performance tests test varIoUs workloads and features measure the performance of specific operations to ensure that most common code paths have not degraded in performance (sometimes kNown as "atomics" tests) test overall performance of specific workloads / features
The following table shows the level of testing performed by Oracle for the varIoUs patch types:
| Interim Patch | PSU,SPU,Bundle | Patch Set Release | |
| Functional | Functional regression tests for the specific area of database functionality affected by the patch. | Complete set of functional regression tests (tests all areas of database functionality). | Complete set of functional regression tests (tests all areas of database functionality). |
| Verification that the fix addresses the kNown symptoms of the BUG issue. | |||
| Stress | None. | Subset of stress tests based on patch content. | Full stress testing. |
| Performance | None. | Workload based performance regression testing. | Full set of performance tests. |
| Other | Install testing in unpatched environment. | Install testing in clean environment. | Install & upgrade testing – many scenarios. |
| Installation using EM CC patching. | “Upgrading” from prevIoUs PSU,bundles. | Deployed and used internally in Oracle before release. | |
| Installation using EM CC patching. | Certification testing. |
Testing Recommendation by Patch Type
Customers are advised to perform testing of patches in a test environment prior to deployment to critical production environments.
The following table gives an overvIEw of the level of testing recommended for each patch type:
| Interim Patch | PSU,SPU | Bundle Patch | Patch Set Release | |
| Install / Rollback | Yes | Yes | Yes | Yes |
| BUG Fix Verification |
| |||
| admin ActivitIEs | Not required | Basic | Basic | Full |
| Application Function | Not required | Core applications only | Core and non-core applications | Full |
| Application Performance | Not required | Not required | Not required | Full |
Where:
Install / Rollback = basic testing that patch apply / rollback works. Patch installation and rollback should be tested for every type of patch.BUG Fix Verification = If you are applying a patch for the purpose of installing a BUG fix then you should verify that the BUG fix addresses the specific BUG issue. For some fixes this may not be feasible - eg: if the fix addresses a rare race condition.
admin ActivitIEs = Software / system administration activitIEs: "Basic" is defined as common activitIEs.
For example,"Basic" admin activitIEs would include valIDating Database and GrID Infrastructure shutdown and startup,valIDating monitoring
Application Function = Functionality of your application. "Core" indicates business critical application functionality.
@L_404_33@Which Patching Method to Use?
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 | 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
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:
(changes involving rollback or install of OJVM PSU to the database will require a complete outage)
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 ResolutionFrequently 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.
| Platform | Environment | DB Version | Method/s |
| Microsoft Platforms | @H_419_1371@Any10.2.0.4 - 12.1.0.2 | windows Bundle,TZ | |
| Unix Platforms | Exadata | 12.1.0.1 - 12.1.0.2 | DBBP,QSFDP for Exadata,OJVM PSU,TZ |
| 11.1.0.7 - 11.2.0.4 | ExaDBBP,TZ | ||
| RAC | 12.1.0.1 - 12.1.0.2 | GI PSU,Combo,TZ | |
| 11.2.0.1 - 11.2.0.4 | GI PSU,TZ | ||
| 10.2.0.4 - 11.1.0.7 | DB PSU,CRS PSU,TZ | ||
| Non-RAC | 12.1.0.1 - 12.1.0.2 | DB PSU,TZ | |
| 10.2.0.4 - 11.2.0.4 | DB PSU,TZ | ||
| Other Platforms | Any | Any | No new bundles |
More information on Proactive Database Patches
| Database Patch Set Update | |
| Short name | DB PSU |
| Target environment/s | Non-RAC DB installations on Unix platforms. Unix DB clIEnt installs. |
| Versions | DB versions 10.2.0.4 - 12.1.0.2 |
| Platform/s | Unix platforms |
| Released | Released quarterly |
| Patch Content | Critical fixes for Database and Database clIEnt. Includes security (cpu) content. No optimizer fixes. |
| See | Note:854428.1 Patch Set Updates for Oracle Products |
| Note:756671.1 Master Note for Database Proactive Patch Program | |
| Recommended Version | Recommend to be on the latest version |
| Notes | |
| Database GrID Infrastructure Patch Set Update | |
| Short name | GI PSU |
| Target environment/s | RAC DB installations on Unix platforms (including single instance RAC). |
| DB Versions | DB versions 11.2.0.1 - 12.1.0.2 |
| Platform/s | Unix platforms |
| Released | Released quarterly |
| Patch Content | Patches include critical fixes for GrID Infrastructure and include the matching DB PSU but *not* any OJVM PSU |
| See | Note:854428.1 Patch Set Updates for Oracle Products |
| Note:756671.1 Master Note for Database Proactive Patch Program | |
| Recommended Version | Recommend to be on the latest version |
| Notes | |
| OJVM Patch Set Update | |
| Short name | OJVM PSU (Oct 2014 also has a separate "JDBC Patch") |
| Target environment/s | Any DB installation using OJVM. |
| DB Versions | DB versions 11.1.0.7,11.2.0.3,11.2.0.4,12.1.0.1 - 12.1.0.2 |
| Platform/s | All platforms. Note that windows platforms have special OJVM PSU overlay patches to apply on top of a windows BP |
| Released | Released quarterly |
| Patch Content | OJVM PSU introduced Oct/2014 but had separate patches for OJVM and JDBC. Jan/2015 onwards the OJVM PSU patch includes JDBC fixes for the database home. |
| See | Note:1929745.1 OJVM PSU information |
| Note:756671.1 Master Note for Database Proactive Patch Program | |
| Recommended Version | Recommend to be on the latest version OR have mitigation patch installed and enabled where that is not possible |
| Notes | There is a "mitigation patch" that can be used in place of OJVM PSU |
| OJVM PSU is NOT RAC Rolling and NOT Standby First installable | |
| Oct 2014 also has a separate "JDBC Patch" | |
| OJVM Patch Set Update "JDBC Patch" (Oct 2014 only) | |
| Short name | JDBC Patch |
| Target environment/s | Any DB,DB clIEnt,instant clIEnt or GrID Infrastructure installation using JDBC |
| DB Versions | JDBC versions 11.1.0.7,12.1.0.1 |
| Platform/s | All platforms |
| Released | Was released as a separate patch just for October 2014 |
| Patch Content | JDBC security fixes |
| See | Note:1929745.1 OJVM PSU information |
| Note:756671.1 Master Note for Database Proactive Patch Program | |
| Recommended Version | Recommend to install this patch wherever JDBC is used,or the latest JDBC component of OJVM PSU |
| Notes | From Jan 2015 onwards the JDBC fixes are included in OJVM PSU patch |
| Combo Patches | |
| Short name | COMBO Patch |
| Target environment/s | Depends on the content - COMBO patches are convenIEnce patches that group patches together |
| DB Versions | DB versions 11.1.0.7,12.1.0.1 - 12.1.0.2 |
| Platform/s | Unix platforms |
| Released | Released quarterly Oct 2014 onwards |
| Patch Content | Includes Patch Set Updates for the different components in a single download |
| See | Note:756671.1 Master Note for Database Proactive Patch Program |
| See notes on the included components (DB PSU,GI PSU,OJVM PSU) | |
| Recommended Version | See recommendation notes on included components |
| Notes | Oct/2014 omitted JDBC patches from the Combo patches |
| windows Database Bundle Patch | |
| Short name | windows Bundle Patch |
| Target environment/s | DB and DB clIEnt installs on Microsoft platforms |
| DB Versions | All DB versions |
| Platform/s | Microsoft platforms only |
| Released | Release interval depends on the database version. |
| Patch Content | Miscellanoues BUG fixes. |
| See | Note:161549.1 Oracle Database,CRS,ASM,Networking and EM Agent Patches for Microsoft Platforms |
| Recommended Version | Recommend to be on latest quarterly release or later |
| Notes | windows Database Bundle Patches do not include OJVM PSU fixes. There are separate OJVM PSU patches available. |
| Database Patch for Exadata | |
| Short name | ExaDBBP (or just BP) |
| Target environment/s | Exadata Database installations |
| DB Versions | DB Versions 11.2.0.1 - 12.1.0.2 |
| Platform/s | Exadata systems only |
| Released | Released quarterly |
| Patch Content | Critical and security content quarterly |
| See | Note:888828.1Exadata Database Machine and Exadata Storage Server Supported Versions |
| Recommended Version | Recommend to be on latest quarterly release |
| Notes | Each quarter the latest Exadata BP is included in the "Quarterly Full Stack Download Patch for Exadata" |
| Quarterly Full Stack Download Patch for Exadata | |
| Short name | QFSDP for Exadata |
| Target environment/s | Exadata systems only |
| DB Versions | DB Versions 11.2.0.1 - 12.1.0.2 |
| Platform/s | Exadata systems only |
| Released | Released quarterly |
| Patch Content | GrID Infrastructure Release Update and other Exadata component patches |
| See | Note:888828.1 Exadata Database Machine and Exadata Storage Server Supported Versions |
| Suggested Level of Testing | Includes more fixes than just PSU fixes. Testing recommended. |
| Recommended Version | Recommend to be on latest release |
| Notes | |
| Database Proactive Bundle Patch | |
| Short name | DBBP |
| Target environment/s | 12.1.0.2 |
| DB Versions | 12.1.0.2 |
| Platform/s | Unix platforms |
| Released | Released monthly. |
| Patch Content | Includes miscellaneous fixes for Engineered Systems along with fixes for Database In-Memory. Critical Patch content is included quarterly. Also includes fixes for the GrID home for Exadata and RAC systems. |
| See | Note:888828.1 Exadata Recommended Patch information |
| Note:756671.1 Master Note for Database Proactive Patch Program | |
| Recommended Version | Recommend to be on the latest quarterly release |
| Notes | From April 2016 onwards new name is "Database Proactive Bundle Patch" Instead of "Database Patch for Engineered Systems and Database In-Memory". |
| Timezone Patches | |
| Short name | TZ patch |
| Target environment/s | DB and DB clIEnt installs where latest timezone data is important |
| DB Versions | All DB versions |
| Platform/s | All platforms |
| Released | Released half yearly |
| Patch Content | Patches only contain timezone data |
| See | Note:412160.1Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone file Patches |
| Recommended Version | No recommendations - use of this patch depends much on the application and whether latest timezone information is important OR not. where it is important recommend to be on the latest release across the enterprise. |
| Notes | There are special consIDerations when patching for timezone updates as communicating systems should use the same TZ information. |
| Database SPU (prevIoUsly kNown as cpu patches) | |
| Short name | SPU (formerly cpu) |
| Target environment/s | DB installs on Unix and VMS platforms |
| DB Versions | All DB Versions up to 11.2.0.4 |
| Platform/s | Unix and VMS platforms |
| Released | Released quarterly |
| Patch Content | SPU patches are critical / security fix content only. This delivery model is not used for 12c onwards - instead critical / security content is included as part of the other delivery models. |
| See | Note:467881.1 Contains links to the latest SPU information |
| Recommended Version | Recommend to use "Database PSU" rather than SPU. If SPU is preferred Recommend to be on latest release |
| Notes | This delivery model is not used for 12c onwards - instead critical / security content is included as part of the other delivery models. |
| CRS Patch Set Update | |
| Short name | CRS bundle |
| Target environment/s | RAC systems up to 11.1.0.7 |
| DB Versions | DB versions 10.2.0.4 to 11.1.0.7 |
| Platform/s | Unix platforms |
| Released | No more releases |
| Patch Content | For CRS stack only. For 11.2.0.1 onwards uses GI PSU instead |
| See | Note:756671.1 Master Note for Database Proactive Patch Program |
| Recommended Version | Upgrade to 11.2 or later |
| Notes | |
| Interim Patches | |
| Short name | Interim Patch (or one-off or PSE) |
| Target environment/s | VarIoUs |
| DB Versions | VarIoUs |
| Platform/s | VarIoUs |
| Released | Released as required / on request |
| Patch Content | Fixes for one or more specific issues |
| See | |
| Recommended Version | It is recommended to avoID installing too many non-standard interim patches. |
| Notes | Functional testing relating to the issue being addressed recommended. |
以上是内存溢出为你收集整理的Oracle Database - Overview of Database Patch Delivery Methods - 12.1.0.2 and older (Doc ID 1962125.1)全部内容，希望文章能够帮你解决Oracle Database - Overview of Database Patch Delivery Methods - 12.1.0.2 and older (Doc ID 1962125.1)所遇到的程序开发问题。
如果觉得内存溢出网站内容还不错，欢迎将内存溢出网站推荐给程序员好友。
欢迎分享，转载请注明来源：内存溢出
微信扫一扫
支付宝扫一扫
评论列表（0条）