Overview of Database Patch Delivery Methods for 12.2.0.1 and greater

古城微笑少年丶 2023-10-08 07:49 15阅读 0赞

<table> 
 <tbody> 
 <tr> 
 <td>&nbsp;Overview of Database Patch Delivery Methods for 12.2.0.1 and greater (Doc ID 2337415.1)</td> 
 <td><img alt="" height="10" src="https://imgconvert.csdnimg.cn/aHR0cHM6Ly9zdXBwb3J0Lm9yYWNsZS5jb20vZXBtb3MvYWRmL2ltYWdlcy90LmdpZg" width="20"></td> 
 </tr> 
 </tbody> 
</table>

--------------------

![aHR0cHM6Ly9zdXBwb3J0Lm9yYWNsZS5jb20vZXBtb3MvYWRmL2ltYWdlcy90LmdpZg][]

<table> 
 <tbody> 
 <tr> 
 <td> <h3>APPLIES TO:</h3> Oracle Database Cloud Schema Service - Version N/A and later Oracle Database Exadata Cloud Machine - Version N/A and later Oracle Cloud Infrastructure - Database Service - Version N/A and later Oracle Database Backup Service - Version N/A and later Oracle Database Cloud Exadata Service - Version N/A and later Information in this document applies to any platform. <h3><a rel="nofollow"></a>PURPOSE</h3> This document gives an overview of the main patch delivery methods used for the Oracle Database Release 12.2.0.1 and later versions. It gives an overview of the main characteristics of Release Updates (Updates) and Release Update Revisions (Revisions). <h3><a rel="nofollow"></a>SCOPE</h3> This 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 annual New Features Release (aka Base Release). It does not discuss the Base Release itself, nor upgrade to Base Release, and only discusses the Oracle Database. It does not discuss Enterprise Manager. <h3><a rel="nofollow"></a>DETAILS</h3> &nbsp; &nbsp; <a rel="nofollow"></a> <h2><a rel="nofollow"></a>Oracle Database - Overview of Database Patch Delivery Methods for 12.2.0.1 and later versions (Doc ID 2337415.1)</h2> This NOTE covers Database Patch Delivery Methods for 12.2.0.1 and later versions. If you are interested in Methods for 12.1.0.2 and older versions, please see MOS&nbsp;<a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=1962125.1" rel="nofollow">Note 1962125.1</a>. <a rel="nofollow"></a> <h4><a rel="nofollow"></a></h4> 
 <ul> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=pjyxehlvk_1380&amp;id=2337415.1#mozTocId395328" rel="nofollow">Oracle Database - Overview of Database Patch Delivery Methods (Doc ID 1962125.1)</a> 
 <ul> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=pjyxehlvk_1380&amp;id=2337415.1#mozTocId653532" rel="nofollow">Post Release Patch Delivery Methods</a></li> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=pjyxehlvk_1380&amp;id=2337415.1#mozTocId981304" rel="nofollow">Types of Proactive Patches</a></li> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=pjyxehlvk_1380&amp;id=2337415.1#mozTocId435153" rel="nofollow">Testing Overview</a></li> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=pjyxehlvk_1380&amp;id=2337415.1#mozTocId71728" rel="nofollow">Testing Recommendation by Patch Type</a></li> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=pjyxehlvk_1380&amp;id=2337415.1#mozTocId782406" rel="nofollow">Which Patching Method to Use?</a></li> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=pjyxehlvk_1380&amp;id=2337415.1#mozTocId208834" rel="nofollow">Switching Between Updates and Revisions</a></li> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=pjyxehlvk_1380&amp;id=2337415.1#mozTocId567559" rel="nofollow">Patch Conflict Resolution</a></li> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=pjyxehlvk_1380&amp;id=2337415.1#mozTocId358762" rel="nofollow">Frequently Asked Questions (FAQ)</a></li> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=pjyxehlvk_1380&amp;id=2337415.1#mozTocId592713" rel="nofollow">Current Database Proactive Patches</a></li> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=pjyxehlvk_1380&amp;id=2337415.1#mozTocId437206" rel="nofollow">Proactive Database Patches by Platform / Environment / Version</a></li> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=pjyxehlvk_1380&amp;id=2337415.1#mozTocId104586" rel="nofollow">More Information on Proactive Database Patches</a></li> 
 </ul></li> 
 </ul><a rel="nofollow"></a> <h3><a rel="nofollow"></a>Post Release Patch Delivery Methods</h3> Oracle provides patches for both proactive and reactive maintenance: 
 <ul> 
 <li>Reactive Patches: 
 <ul> 
 <li>are usually delivered as “Interim Patches”</li> 
 <li>were historically known as “one-off” patches</li> 
 <li>are provided on demand for a given “defect, version, platform” combination</li> 
 <li>go through basic sanity tests</li> 
 <li>Regression fixes that meet all other content criteria will be included in subsequent Updates and Revisions (if there is one)</li> 
 <li>All other fixes will be reviewed and considered for a subsequent Update.</li> 
 </ul></li> 
 </ul> 
 <ul> 
 <li>Proactive Patches 
 <ul> 
 <li>address high impact bugs that affect a given configuration</li> 
 <li>contain proven low risk fixes</li> 
 <li>go through extra levels of testing, determined by the feature(s) affected</li> 
 <li>are available on "My Oracle Support" by clicking on the "Patches &amp; Updates" tab</li> 
 </ul></li> 
 </ul><a rel="nofollow"></a> <h3><a rel="nofollow"></a>Types of Proactive Patches</h3> There are different types of proactive patches available. This section gives a summary of the main proactive patching methods: 
 <ul> 
 <li>Release Update (Update) 
 <ul> 
 <li>a cumulative collection of fixes to address bugs in a given feature, product, or configuration For example: Database Release Update,&nbsp;and&nbsp;Grid Infrastructure Release Update</li> 
 <li>may span multiple stack components For example: "Grid Infrastructure Release Update" includes fixes both Database and Grid Infrastructure</li> 
 <li>delivered on pre-defined quarterly schedule</li> 
 <li>are always RAC Rolling and Standby First installable</li> 
 <li>includes the latest security fixes</li> 
 <li>high-value, low-risk non-security fixes</li> 
 </ul></li> 
 </ul> 
 <ul> 
 <li>Release Update Revision (Revision) 
 <ul> 
 <li>a cumulative collection of fixes to address bugs in a given feature, product, or configuration For example:&nbsp;Database Release Update Revision,&nbsp;and&nbsp;Grid Infrastructure Release Update Revision</li> 
 <li>may span multiple stack components For example: "Grid Infrastructure Release Update" includes fixes both Database and Grid Infrastructure</li> 
 <li>delivered on pre-defined quarterly schedule</li> 
 <li>are always RAC Rolling and Standby First installable</li> 
 <li>extends the lifetime of an Update up to six months (typically 2 Revisions)</li> 
 <li>includes only regression fixes and security fixes &nbsp;</li> 
 </ul></li> 
 <li>"Quarterly Full Stack Download Patch" / "Combo Patch" 
 <ul> 
 <li>delivers a number of different patches packaged together For Example: 
 <ul> 
 <li>"Quarterly Full Stack Download Patch for Exadata" includes "Quarterly Grid Infrastructure Release Update" along with OJVM Update and other Exadata system patches in a single download.</li> 
 <li>"Combo Patch of OJVM Release Update and Database Release Update.</li> 
 </ul></li> 
 </ul></li> 
 <li>Other Proactive Patches 
 <ul> 
 <li>Oracle produces some proactive patches for very specific purposes outside of the normal Update/Revision 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"</li> 
 </ul></li> 
 </ul>&nbsp; When considering the Database patch content for the Update and for the Revision, it is often asked "Which has the more recent or more 'up-to-date' content?" Or in other words "Which is the sub-set and which is the super-set?". The answer depends upon your perspective. From the perspective of a set of two Revisions that are provided 3 months apart, for a particular Update (for example 18.3.1 and 18.3.2 for 18.3.0), each Revision has exactly the same content as its older, associated Update - plus more. Each Revision additionally has regression fixes and newer security Bug fixes that the older, associated Update does not have. From this perspective, the Revision is a super-set of the older, associated Update. It can be visualized like this: 
 <blockquote> 
 <table> 
 <tbody> 
 <tr> 
 <td style="vertical-align:bottom;">&nbsp;</td> 
 <td> Revision 18.3.1 </td> 
 <td style="vertical-align:bottom;">&nbsp;</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:bottom;">&nbsp;</td> 
 <td> Update 18.3.0 </td> 
 <td>&nbsp;</td> 
 </tr> 
 </tbody> 
 </table> 
 </blockquote> &nbsp; However, from the perspective of the three patches (one Update, and two Revisions) that are provided at the same time each quarter (for example 18.4.0, 18.3.1, and 18.2.2) all have the exact same, newest, security Bug fixes. But only the Update has the newest non-security Bug fixes. From this perspective, the Update is a super-set of the two Revisions that are issued at the same time. It can be visualized like this: 
 <blockquote> 
 <table> 
 <tbody> 
 <tr> 
 <td style="vertical-align:bottom;">&nbsp;</td> 
 <td> Update 18.4.0 </td> 
 <td style="vertical-align:bottom;">&nbsp;</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:bottom;">&nbsp;</td> 
 <td> Revision 18.3.1 </td> 
 <td>&nbsp;</td> 
 </tr> 
 </tbody> 
 </table> 
 </blockquote> &nbsp; Updates and Revisions are designed to allow customers to change back and forth as desired. 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. <a rel="nofollow"></a> <h3><a rel="nofollow"></a>Testing Overview</h3> Oracle performs different types of testing on various patch types prior to their release: 
 <ul> 
 <li>Functional tests</li> 
 <li> 
 <ul> 
 <li>Test specific areas of functionality against expected outcomes. An "area" may be a feature or subset of a feature (eg: Advanced Queueing or a specific functionality of Advanced Queueing)</li> 
 <li>Functional tests include regression testing to ensure that results and behaviour of specific operations are as expected.</li> 
 </ul></li> 
 </ul> 
 <ul> 
 <li>Stress tests 
 <ul> 
 <li>test resilience of the database when pushed to its limit in resource utilization and in specific configurations</li> 
 <li>heavy destructive tests under high load</li> 
 </ul></li> 
 </ul> 
 <ul> 
 <li>Performance tests 
 <ul> 
 <li>test various workloads and features</li> 
 <li>measure the performance of specific operations to ensure that most common code paths have not degraded in performance (sometimes known as "atomics" tests)</li> 
 <li>test overall performance of specific workloads / features</li> 
 </ul></li> 
 </ul> The following table shows the level of testing performed by Oracle for the various patch types: 
 <table> 
 <tbody> 
 <tr> 
 <td style="vertical-align:middle;">&nbsp;</td> 
 <td style="vertical-align:top;">Interim Patch</td> 
 <td style="vertical-align:top;">Update and Revision</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:middle;">Functional</td> 
 <td style="vertical-align:top;">Functional regression tests for the specific area of database functionality affected by the patch.</td> 
 <td style="vertical-align:top;">Complete set of functional regression tests (tests all areas of database functionality).</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Verification that the fix addresses the known symptoms of the bug issue.</td> 
 <td style="vertical-align:top;">&nbsp;</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:middle;">Stress</td> 
 <td style="vertical-align:top;">None.</td> 
 <td style="vertical-align:top;">Subset of stress tests based on patch content.</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:middle;">Performance</td> 
 <td style="vertical-align:top;">None.</td> 
 <td style="vertical-align:top;">Workload based performance regression testing.</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:middle;">Other</td> 
 <td style="vertical-align:top;">Install testing in unpatched environment.</td> 
 <td style="vertical-align:top;">Install testing in unpatched environment, and the most recent previously released Update/Revision.</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Installation using EM CC patching.</td> 
 <td style="vertical-align:top;">Installation using EM CC patching.</td> 
 </tr> 
 </tbody> 
 </table>&nbsp; <a rel="nofollow"></a> <h3><a rel="nofollow"></a>Testing Recommendation by Patch Type</h3> 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: 
 <table> 
 <tbody> 
 <tr> 
 <td>&nbsp;</td> 
 <td>Interim Patch</td> 
 <td>Update and Revision</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:middle;">Install / Rollback</td> 
 <td>Yes</td> 
 <td>Yes</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:middle;">Bug Fix Verification</td> 
 <td colspan="2"> Where possible and relevant </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:middle;">Admin Activities</td> 
 <td>Not required</td> 
 <td>Basic</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:middle;">Application Function</td> 
 <td>Not required</td> 
 <td>Core and non-core applications</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:middle;">Application Performance</td> 
 <td>Not required</td> 
 <td>Not required</td> 
 </tr> 
 </tbody> 
 </table>Where: 
 <ul> 
 <li>Install / Rollback = basic testing that patch apply / rollback works. Patch installation and rollback should be tested for every type of patch. &nbsp;</li> 
 <li>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. 
 <ul> 
 <li>For some fixes this may not be feasible - eg: if the fix addresses a rare race condition. &nbsp;</li> 
 </ul></li> 
 <li>Admin Activities = Software / system administration activities: 
 <ul> 
 <li>"Basic" is defined as common activities. For example, "Basic" admin activities would include validating Database and Grid Infrastructure shutdown and startup, validating monitoring &nbsp;</li> 
 </ul></li> 
 <li>Application Function = Functionality of your application. "Core" indicates business critical application functionality. &nbsp;</li> 
 </ul><a rel="nofollow"></a> <h3><a rel="nofollow"></a>Which Patching Method to Use?</h3> Oracle recommends that customers stay current with Updates. By doing this they minimize the chance of encountering known bugs and security vulnerabilities. Staying current with Updates reduces the likelihood of requiring separate interim one-off patches which lead to unique software baselines and potential for ongoing costly patch maintenance. Some customers may have reached a stable state and want to prioritize security updates over functional fixes. In such cases, they may choose to apply Revisions. When they apply Revision Release.Update.1, they lag with the Update content by 3 months. When they apply Revision Release.Update.2, they lag with the Update content by 6 months. By choosing to lag on taking new Update content by 3 or 6 months, customers can take a more conservative approach to Database software maintenance, but they still risk the chance of hitting known issues fixed in the most recent Updates. 
 <table> 
 <tbody> 
 <tr> 
 <th>RELEASE</th> 
 <th>Exadata</th> 
 <th>Exadata (when patching just Database and Grid Infrastructure)</th> 
 <th>All non-Exadata (RAC)</th> 
 <th>All non-Exadata (non-RAC)</th> 
 <th>Windows</th> 
 </tr> 
 <tr> 
 <td>12.2.0.1</td> 
 <td>Quarterly Full Stack Download Patch for Exadata</td> 
 <td>Release Update / Release Update Revision</td> 
 <td>Release Update / Release Update Revision</td> 
 <td>Release Update / Release Update Revision</td> 
 <td>Windows Database Bundle Patch</td> 
 </tr> 
 </tbody> 
 </table>Additionally 
 <ul> 
 <li>In all situations, be sure to install the relevant OJVM Update &nbsp;</li> 
 <li>Install interim patches only for specific issues that you know will apply to your environment. 
 <ul> 
 <li>Keep the number of interim patches installed to a minimum.</li> 
 <li>Installing the latest Update is a good way to reduce the need for interim patches.</li> 
 </ul></li> 
 </ul>&nbsp; <a rel="nofollow"></a> <h3><a rel="nofollow"></a>Switching Between Updates and Revisions</h3> Oracle supports switching between Updates and Revisions. It is recommended to apply an Update/Revision that is a super set of the Update/Revision currently installed so that fixes are not lost. At a high-level, the process is as follows: 
 <ul> 
 <li>Make note of the interim patches installed in the Oracle home</li> 
 <li>Check for conflicts between the installed interim patches and the target Update/Revision</li> 
 <li>As needed, request new interim patches.</li> 
 <li>When the interim patches are available, install the target Update/Revision and any required interim patches.</li> 
 </ul><a rel="nofollow"></a> <h3><a rel="nofollow"></a>Patch Conflict Resolution</h3> 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 (Quarterly Exadata Patch, Update, and Revision) 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: 
 <ul> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=1941934.1" rel="nofollow">Document:1941934.1</a>&nbsp;My Oracle Support Patch Conflict Checker Overview&nbsp;[Video]</li> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=1091294.1" rel="nofollow">Document:1091294.1</a>&nbsp;How to Use the My Oracle Support Conflict Checker Tool for Patches Installed with OPatch [Video]</li> 
 <li><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=1321267.1" rel="nofollow">Document:1321267.1</a>&nbsp;Database Patch Conflict Resolution</li> 
 </ul><a rel="nofollow"></a> <h3><a rel="nofollow"></a>Frequently Asked Questions (FAQ)</h3> 
 <ul> 
 <li>Do proactive patches include optimizer fixes? 
 <ul> 
 <li>"Database Patch for Exadata"&nbsp;can&nbsp;include optimizer fixes for wrong results issues, but only in a form that allows them to be individually enabled/disabled as required.</li> 
 <li>"Windows Database Bundle Patch"&nbsp;can&nbsp;include optimizer fixes</li> 
 <li>"Database Updates/Revisions"&nbsp;can&nbsp;include optimizer fixes for wrong results issues, but only in a form that allows them to be individually enabled/disabled as required. For more information, please refer to&nbsp;<a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=2147007.1" rel="nofollow">Note 2147007.1</a>, "Automatic Fix Control Persistence (FCP) for Database Proactive Bundle Patch" &nbsp;</li> 
 </ul></li> 
 <li>How can I tell what patching method an installation uses? 
 <ul> 
 <li>Review the opatch lsinventory output to see what patches are applied. Update patches and Revision patches include a description of the patch name/version in the output. &nbsp;</li> 
 </ul></li> 
 <li>What is the difference between "Windows Database Bundle Patch" and "QFSDP for Exadata" etc.. ? 
 <ul> 
 <li>These bundles are targeted at different environments. The latest versions will include the same Update 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. &nbsp;</li> 
 </ul></li> 
 <li>Do proactive patches affect the database version as reported in tracefiles and database views like V$VERSION? 
 <ul> 
 <li>For 12.2.0.1 the patch level is reflected in the opatch lsinventory data, and for some patch types is reflected in DBA_REGISTRY or DBA_REGISTRY_HISTORY &nbsp;</li> 
 </ul></li> 
 </ul><a rel="nofollow"></a> <h3><a rel="nofollow"></a>Current Database Proactive Patches</h3> The following tables give information on currently available proactive database related patches, including some patch types that are no longer produced. NOTE: For Standard Edition, whether the DBBP is an applicable choice or not differs by its version. Please check README to determine if the DBBP is an applicable choice. <a rel="nofollow"></a> <h3><a rel="nofollow"></a>Proactive Database Patches by Platform / Environment / Version</h3> Short names used in the "Method/s" column of the following table are expanded on in the next section. 
 <table> 
 <tbody> 
 <tr> 
 <td>Platform</td> 
 <td>Environment</td> 
 <td>DB Version</td> 
 <td>Method/s</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:middle;">Unix Platforms</td> 
 <td style="vertical-align:middle;">Exadata</td> 
 <td>12.2.0.1</td> 
 <td>QFSDP for Exadata, OJVM Update/Revision, TZ</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:middle;">RAC</td> 
 <td>12.2.0.1</td> 
 <td>GI Update/Revision, OJVM Update/Revision, Combo, TZ</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:middle;">Non-RAC</td> 
 <td>12.2.0.1</td> 
 <td>DB Update/Revision, OJVM Update/Revision, Combo, TZ</td> 
 </tr> 
 <tr> 
 <td>Windows Platforms</td> 
 <td style="vertical-align:middle;">All</td> 
 <td>12.2.0.1</td> 
 <td>Windows Bundles, TZ</td> 
 </tr> 
 </tbody> 
 </table><a rel="nofollow"></a> <h3><a rel="nofollow"></a>More Information on Proactive Database Patches</h3> 
 <table> 
 <tbody> 
 <tr> 
 <td colspan="2">OJVM Release Update</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Short Name</td> 
 <td>OJVM Update</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Target environment/s</td> 
 <td>Any DB installation using OJVM.</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">DB Versions</td> 
 <td>DB versions 12.2.0.1 and later</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Platform/s</td> 
 <td>All platforms.</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Released</td> 
 <td>Released Quarterly</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Patch Content</td> 
 <td>OJVM and JDBC fixes for the database home.</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">See</td> 
 <td><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=1929745.1" rel="nofollow">Note:1929745.1</a>&nbsp;OJVM Update Information</td> 
 </tr> 
 <tr> 
 <td>&nbsp;</td> 
 <td><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=756671.1" rel="nofollow">Note:756671.1</a>&nbsp;Master Note for Database Proactive Patch Program</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Recommended Version</td> 
 <td>Recommend to be on the latest quarterly OJVM Update</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Notes</td> 
 <td>Windows platforms have special OJVM Update overlay patches to apply on top of a Windows BP</td> 
 </tr> 
 <tr> 
 <td>&nbsp;</td> 
 <td>OJVM Update is NOT RAC Rolling and NOT Standby First installable.</td> 
 </tr> 
 <tr> 
 <td>&nbsp;</td> 
 <td>&nbsp;</td> 
 </tr> 
 <tr> 
 <td colspan="2">Combo Patches</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Short Name</td> 
 <td>COMBO Patch</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Target environment/s</td> 
 <td>12.2 Database homes. This includes Exadata, RAC, and non-RAC</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">DB Versions</td> 
 <td>DB versions 12.2.0.1</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Platform/s</td> 
 <td>Unix platforms</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Released</td> 
 <td>Released quarterly</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Patch Content</td> 
 <td>Includes Release Updates for the different components in a single download</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">See</td> 
 <td><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=756671.1" rel="nofollow">Note:756671.1</a>&nbsp;Master Note for Database Proactive Patch Program</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Recommended Version</td> 
 <td>Recommend to be on the latest quarterly Combo patch</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Notes</td> 
 <td>&nbsp;</td> 
 </tr> 
 <tr> 
 <td>&nbsp;</td> 
 <td>&nbsp;</td> 
 </tr> 
 <tr> 
 <td colspan="2">Windows Database Bundle Patch</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Short Name</td> 
 <td>Windows Bundle Patch</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Target environment/s</td> 
 <td>DB and DB client installs on Microsoft platforms</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">DB Versions</td> 
 <td>All DB versions</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Platform/s</td> 
 <td>Microsoft platforms only</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Released</td> 
 <td>Release interval depends on the database version.</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Patch Content</td> 
 <td>Miscellanoues bug fixes.</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">See</td> 
 <td><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=161549.1" rel="nofollow">Note:161549.1</a>&nbsp;Oracle Database, CRS, ASM, Networking and EM Agent Patches for Microsoft Platforms</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Recommended Version</td> 
 <td>Recommend to be on latest quarterly release or later</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Notes</td> 
 <td>Windows Database Bundle Patches do not include OJVM Update fixes. There is a separate OJVM Update patch available.</td> 
 </tr> 
 <tr> 
 <td>&nbsp;</td> 
 <td>&nbsp;</td> 
 </tr> 
 <tr> 
 <td colspan="2">Quarterly Full Stack Download Patch for Exadata</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Short Name</td> 
 <td>QFSDP for Exadata</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Target environment/s</td> 
 <td>Exadata systems only</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">DB Versions</td> 
 <td>DB Versions 12.2.0.1 and later</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Platform/s</td> 
 <td>Exadata systems only</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Released</td> 
 <td>Released quarterly</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Patch Content</td> 
 <td>Grid Infrastructure Release Update and other Exadata component patches</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">See</td> 
 <td><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=888828.1" rel="nofollow">Note:888828.1</a>&nbsp;Exadata Database Machine and Exadata Storage Server Supported Versions</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Recommended Version</td> 
 <td>Recommend to be on latest quarterly QFSDP</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Notes</td> 
 <td>&nbsp;</td> 
 </tr> 
 <tr> 
 <td>&nbsp;</td> 
 <td>&nbsp;</td> 
 </tr> 
 <tr> 
 <td colspan="2">Release Update</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Short Name</td> 
 <td>Update</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Target environment/s</td> 
 <td>12.2 DB installs on Exadata. All 12.2 Database and Grid homes. This includes Exadata, RAC and non-RAC.</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">DB Versions</td> 
 <td>12.2.0.1 onwards</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Platform/s</td> 
 <td>Unix platforms</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Released</td> 
 <td>Released quarterly.</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Patch Content</td> 
 <td>High-value, low-risk fixes, Security fixes, and Regression fixes</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">See</td> 
 <td><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=888828.1" rel="nofollow">Note:888828.1</a>&nbsp;Exadata Recommended Patch Information</td> 
 </tr> 
 <tr> 
 <td>&nbsp;</td> 
 <td><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=756671.1" rel="nofollow">Note:756671.1</a>&nbsp;Master Note for Database Proactive Patch Program</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Recommended Version</td> 
 <td>Recommend to be on the latest quarterly release update</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Notes</td> 
 <td>&nbsp;</td> 
 </tr> 
 <tr> 
 <td>&nbsp;</td> 
 <td>&nbsp;</td> 
 </tr> 
 <tr> 
 <td colspan="2">Release Update Revision</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Short Name</td> 
 <td>Revision</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Target environment/s</td> 
 <td>All 12.2 Database and Grid homes. This includes Exadata, RAC and non-RAC</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">DB Versions</td> 
 <td>12.2.0.1 onwards</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Platform/s</td> 
 <td>Unix platforms</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Released</td> 
 <td>Released quarterly.</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Patch Content</td> 
 <td>Security fixes and Regression fixes</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">See</td> 
 <td><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=888828.1" rel="nofollow">Note:888828.1</a>&nbsp;Exadata Recommended Patch Information</td> 
 </tr> 
 <tr> 
 <td>&nbsp;</td> 
 <td><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=756671.1" rel="nofollow">Note:756671.1</a>&nbsp;Master Note for Database Proactive Patch Program</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Recommended Version</td> 
 <td>See "Release Update" section above</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Notes</td> 
 <td>&nbsp;</td> 
 </tr> 
 <tr> 
 <td>&nbsp;</td> 
 <td>&nbsp;</td> 
 </tr> 
 <tr> 
 <td colspan="2">Timezone Patches</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Short Name</td> 
 <td>TZ patch</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Target environment/s</td> 
 <td>DB and DB client installs where latest timezone data is important</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">DB Versions</td> 
 <td>All DB versions</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Platform/s</td> 
 <td>All platforms</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Released</td> 
 <td>Released half yearly</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Patch Content</td> 
 <td>Patches only contain timezone data</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">See</td> 
 <td><a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=2337415.1&amp;id=412160.1" rel="nofollow">Note:412160.1</a>&nbsp;Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Recommended Version</td> 
 <td>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.</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Notes</td> 
 <td>There are special considerations when patching for timezone updates as communicating systems should use the same TZ information.</td> 
 </tr> 
 <tr> 
 <td>&nbsp;</td> 
 <td>&nbsp;</td> 
 </tr> 
 <tr> 
 <td colspan="2">Interim Patches</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Short Name</td> 
 <td>Interim Patch (or one-off or PSE)</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Target environment/s</td> 
 <td>Various</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">DB Versions</td> 
 <td>Various</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Platform/s</td> 
 <td>Various</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Released</td> 
 <td>Released as required / on request</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Patch Content</td> 
 <td>Fixes for one or more specific issues</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">See</td> 
 <td>&nbsp;</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Recommended Version</td> 
 <td>It is recommended to avoid installing too many non-standard interim patches.</td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;">Notes</td> 
 <td>Functional testing relating to the issue being addressed recommended.</td> 
 </tr> 
 </tbody> 
 </table></td> 
 </tr> 
 </tbody> 
</table>

![aHR0cHM6Ly9zdXBwb3J0Lm9yYWNsZS5jb20vZXBtb3MvYWRmL2ltYWdlcy90LmdpZg][]![aHR0cHM6Ly9zdXBwb3J0Lm9yYWNsZS5jb20vZXBtb3MvYWRmL2ltYWdlcy90LmdpZg][]Didn't find what you are looking for?![aHR0cHM6Ly9zdXBwb3J0Lm9yYWNsZS5jb20vZXBtb3MvYWRmL2ltYWdlcy90LmdpZg][]

![aHR0cHM6Ly9zdXBwb3J0Lm9yYWNsZS5jb20vZXBtb3MvYWRmL2ltYWdlcy90LmdpZg][]

[aHR0cHM6Ly9zdXBwb3J0Lm9yYWNsZS5jb20vZXBtb3MvYWRmL2ltYWdlcy90LmdpZg]: https://imgconvert.csdnimg.cn/aHR0cHM6Ly9zdXBwb3J0Lm9yYWNsZS5jb20vZXBtb3MvYWRmL2ltYWdlcy90LmdpZg