加入收藏 | 设为首页 | 会员中心 | 我要投稿 济源站长网 (https://www.0391zz.cn/)- 数据工具、数据仓库、行业智能、CDN、运营!
当前位置: 首页 > 站长百科 > 正文

Oracle Database - Overview of Database Patch Delivery Method

发布时间:2020-12-31 04:30:56 所属栏目:站长百科 来源:网络整理
导读:介绍各种补丁集的使用方法: 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

?

?

BP

?

?

?

?

PSU

?

?

?

(编辑:济源站长网)

【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容!

副标题[/!--empirenews.page--]

介绍各种补丁集的使用方法:

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.

PURPOSE

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.

SCOPE

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 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" tab

Types 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 components
      For 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:

热点阅读